3 ms·
CVR overwrite is bad news here. The crew knew this was a serious problem when it happened, there's no way they should have allowed the CVR, crucial evidence of
by tialaramex 8y ago
CVR overwrite is bad news here. The crew knew this was a serious problem when it happened, there's no way they should have allowed the CVR, crucial evidence of exactly what happened, to be overwritten.
Perhaps the full report will have more detail on this, as it stands I have to believe somebody made the decision to overwrite this because they thought it'd be better if it didn't exist. Whether that's the crew, their bosses or other staff, somebody managed to go from "serious incident, preserve evidence" to "maximum ass covering" and that person or persons are an obstacle to effective investigation and thus to safe air travel.
- walrus01 8y agoIf I understand CVR tech correctly, it's running and constantly overwriting the storage in a loop whenever the plane is powered up. A lot of airplanes are 10, 15, 20 years old. CVR are based on some pretty old late 1980s technology, it's not like a modern flash based storage system with effectively infinite capacity for stereo 44KHz audio (64, 128GB, etc). There's maybe 1 or 2 hours of recording time, max.
- sokoloff 8y agoSubject aircraft, C-FKCK, is a 1991 A320, which is only required to have a 30 minute CVR loop. (I don't know which exact CVR it was equipped with, of course.) By the time the aircraft goes around, is resequenced, completes the second approach, lands, taxis in, and shuts down, much of the initial approach setup conversation may have already been overwritten anyway. I wouldn't jump to the assumption that there was malicious intent in the fact that the CVR was overwritten. (I also wouldn't want the crew to stop the CVR recording only to have a second, more serious incident on the same flight that would then go unrecorded.)
- cpitVoxRec 8y agoThey actually do clearly state in this PDF that a degree of fault lies in the crew being compromised by fatigue. Operating for 19 hours straight definitely places an individual in an area where one can be fighting to pay strict attention, even when it really counts. There's also plenty of communication with Air Traffic Control in the tower, and not a whole lot of gaps to introduce significant mystery, so it's pretty unlikely that there would be anything earth shattering on the cockpit voice recorder.
- tialaramex 8y agoWhat I'd expect the CVR to provide good evidence of is the extent to which crew were actually doing the checks that should have caught this error, and their reaction when they belatedly discovered their true position. Without even trying to mislead investigators a human will report a sanitised version of events when not cued by facts. "Then I scratched my arse and sniffed my finger" is not going to appear in this sanitised version of events even if true. Neither is "I glanced at the panel, I know I'm supposed to scan it, but usually anything important flashes red". The tower log helps, CVR is better, and CCTV better again. It also really helps to get into the routine of analysing this stuff. If your aircrew routinely skip steps 4, 18 and 23 from the checklist, only finding that out when 200 passengers die in a crash is stupid. Let's find out now. That needs lots of heavy lifting, pilots have to trust the airlines not to fire them for ordinary human frailties, and airlines have to accept that their pilots are human and "But the manual says not to do that" doesn't make it stop happening magically. You're right that fatigue is an obvious element here, and there are several technical countermeasures mentioned. I definitely don't want to come across as believing in a conspiracy to hide the facts, but on the other hand I struggle to believe that it took over 30 minutes to get this thing back down after the incident and so the overwrite was not a decision. And if we agree it was a decision, it was a seriously bad one that should not be repeated.
- cpitVoxRec 8y agoI struggle to believe that it took over 30 minutes to get this thing back down after the incident If your inferring that a 30 minute offset was introduced, in order to dump the stale audio buffer, before permitting access to the CVR instrument on the ground, I'd offer the idea that there were 4 other planes on the taxiway, waiting to take off, and that the intervening 30 minutes could be eaten up by letting those planes depart, based on an array of other factors. A concerted effort to dump the recorder buffer would require the participation of more than just the flight crew, since it manipulates the standing traffic pattern. Not an impossibility, and we know that in-group "walls of silence" definitely accumulate in high-intensity industries, but the air traffic control audio suggests a really minor transgression of situational awareness, even if the circumstances are assuredly unforgiving ones. In the radio audio, the pilot clearly states that he's noticing lights on what he imagines to be his runway, and asks for confirmation as to what they might be. The tower reaffirms that he's all clear. Only then does a pilot from one of the planes on the ground speak up, and complain. At that moment, both ATC and the plane realize the error. It's arguable that the pilot anticipated a likely go-around, based on intuition that the lights he was observing were definitely other planes, and that what appears to be an extremely close call proves it's own margin of error as reasonable, given that the participants recovered from the error.