> I'm surprised that remote video cameras aren't used by tower controllers. I guess I'm surprised that it took so long for the pilots to see that there were other planes where they were landing. And even on the lowest intensity setting, runway lights are brighter than taxiway lights. There are probably good reasons for not having the Xes. [31], C-FKCK, the aircraft involved in the incident, in June 2007, Air Canada A320 nearly lands on taxiway! These kinds of cameras usually live at the back of a tube that also serves as a sun shade and weather shelter. Reminds me how those "Simulator" games are so popular in Germany! Photo, courtesy of Air Canada. The report faults Air Canada for reporting too late and erasing the voice record, but notes that the NTSB only requires notification when an aircraft lands or departs on a taxiway, or when a collision is avoided after a runway incursion, and neither happened. He tries to give you the facts from the source materials but maybe he got it wrong, maybe he is out of date. In your own life and goings about, it's sometimes interesting to do a failure analysis and you'll often find you experienced a cascade. Trying to pick out an airplane against the ground is different from detecting an object in the air, which doesn't generally reflect radio back, and detecting the ground, which does reflect. The air traffic controller misses a few chances to notice that something isn't right but when the pilot on the taxiway says in plain English, 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. It's kind of baffling to me that there's a system for detecting collisions with other airplanes in the sky (TCAS) and a system for detecting collisions with the ground (EGPWS) but not system for detecting collisions with other airplanes on the ground. make them jagged? This was 100% my read as well. According to the NTSB, Air Canada Flight 759 was at just 85 feet of altitude when the pilots powered up its engines to abort the landing. When under pressure, we go with the strongest signal. A magnifying glass. Imagine a box at the back of the toilet, out of which the seat extends (full oval, not a horseshoe). "[1][3] AC759 had already started to climb before the go-around order. The very first thing I thought of upon reading your comment "The list of things tried so far to resolve the issue..." was "What about a big lighted 'x'?" Our market right now is general aviation and business jets. Given the high approach speeds, this is probably a non-trivial problem. Also that they cite fatigue / circadian low as one of the core causes. Here's a video of the system on a G1000 (meant for smaller planes) skip to 0:45ish https://www.youtube.com/watch?v=V2bswm0w4cY. During an approach at night, scarce sensory input is interpolated to form a full model by the brain. This process can easily lead to nominally weird things like blue lights being percieved as white. All four engines have stopped. Please include full name, physical address, end use and confirmation that they will not sell or transfer this item to any party in Cuba, Iran, North Korea, Sudan or Syria. This easily could have killed a thousand people. A lot of airplanes are 10, 15, 20 years old. Exactly my question. Short of that, we can't fix it even if we know it's wrong. I get excited seeing stories about aviation on HN because it's something I work on every day. It's 9000+ feet long. Take a look. Multiple passenger planes on the taxiway taken out by a passenger jet. Small airports or bad weather at night are a different story - I would not fly into a new airport the first time in those conditions. Also, don’t buy American and you don’t have this problem. There are lots of systems that are available to avoid that (ILS, GPS etc.) This isn't supposed to be subtle, and I haven't ever experienced it to be subtle. Don't the runways have their names labeled in lights near the entrances? According to the report, the incident was due to the flight crew “ineffective review of notice to airmen (NOTAM) information before the flight and during the approach briefing.” The failure was mainly blamed on fatigue from both pilots and Air Canada’s (ADH2) “presentation of approach procedure and NOTAM information.”. I hope you have a great day! A retired pilot stated the runway confusion that almost happened "probably came close to the greatest aviation disaster in history"[2][3][4][5] as five airplanes and potentially over 1,000 passengers were at imminent risk. Fatigue and stress would contribute to ward off looming decoherence such as "why are the lights on 28L redder than on 28R?" [23], In a September 25, 2018 board meeting, the NTSB cited as probable cause the pilots misunderstanding the taxiway for runway 28R as they overlooked the 28L closure buried in the NOTAM, and as contributing factors: not taking advantage of the ILS, which was not tuned, in the flight management system (FMS) visual approach; and pilot fatigue. As for accuracy, we have minimum levels of GPS figure of merit where there's enough certainty to issue alerts. It didn't matter that the whole world was telling him it was a taxiway because he was so sure it was a runway. Automatically monitoring an ILS approach is not that difficult from the cockpit if the frequency can be sent via ADS-B. "Then I scratched my arse and sniffed my finger" is not going to appear in this sanitised version of events even if true. It's an interesting dilemma. Although this pic is blurry, this is SFO with both runways open: Large airports have fancy lighting schemes and are pretty obvious in good weather. That means the Air Canada jet came within feet of colliding with three fueled and loaded widebody airliners. The letter F. A play button in the shape of a television screen. Specialized in Defense Aviation and Aviation Safety. This is a flagged and lighted obstruction half a mile way that is 34 feet above ground level. Instead of lining up for runway 28L and 28R, the Air Canada jet lined up to land on taxiway C, which runs parallel to the runways. Daardoor veranderen de wetten voor ondernemers rond energiebesparing continu. airliners? Could they have seen what was on the ground sooner if they'd looked through binoculars briefly (after noticing unexpected lights?). Wat moet je weten? Air Canada Flight 759 nearly landed on a taxiway where four airliners were awaiting takeoff. I think the guy who did the classic SR71 story about upstaging everyone on some California flyby noted this pretty well - even in the times of near peril pilots and ATC will be the cool-as-steel that keep everyone calm. 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. The money can't be an issue. What happened here is that the pilots were locked into a wrong model: In an environment with very little light there is no visual source to compare taxiway lighting against. The key is preventing nuisance alerts when the pilot is just flying around and happens to be aligned with a runway. Cadet training programs for type and non-type rated pilots. Strobes usually aren't on while on the ground or at least probably shouldn't be. Good question. Deze informatie wordt je aangeboden door een van onze adverteerders. Something about this particular situation definitely is off. Even though the pilots didn’t see any aircraft, there were, in fact, four fully loaded jets sitting on taxiway C awaiting takeoff. 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. However, I doubt it's cheap and there might be cheaper ways to do it that don't leverage the two systems you've mentioned. Open, consumer information sources like flightaware.com alone had the answer to the questions you're asking, long ago. Multiple failures resulting in a catastrophic failure. Air Canada Flt. The biggest aviation conference and awards in the region. 759 was cleared to land on Runway 28R, but mistook Taxiway C, where four airplanes were lined up for departure, as the runway. Along with the report, the NTSB released a set of photos and diagrams showing what transpired that evening. What's your market? Don't care, not my problem now, let their shareholders worry about it. Delta Air Lines took delivery of a special Airbus A220, as the aircraft is the first Mobile, Alabama, United States-buil... All Nippon Airways (ANA) made a decision on 21th to cut 25 to 30 large aircraft mainly for long-haul international route... Brazil, like Mexico, was one of the first countries to open up its airspace in South America. Had a project once where we were trying to parse NOTAMs so we could program a GPS with a warning indicator if you were about to fly into a restricted airspace. And some interesting alternative takes (https://opsfox.net), which have their own problems. “They also stated that they did not recall seeing aircraft on taxiway C but that something did not look right to them.”. What is the chance of false positives (or negatives) due to out of date databases? Light aircraft? In the beginning of July 2017, an Air Canada Airbus A320 operating flight, According to the report, the incident was due to the flight crew “ineffective review of notice to airmen (NOTAM) information before the flight and during the approach briefing.” The failure was mainly blamed on fatigue from both pilots and Air Canada’s (, Canada’s pilot-fatigue rules slammed by unions. [11] AC759 disappeared from the local controller's ASSC display for twelve seconds, between 11:55:52 and 11:56:04 p.m. local time (from shortly after the AC759 pilot asked for confirmation that 28R was clear, to the time the UA001 pilot noted that AC759 was lined up for Taxiway C), as AC759 was too far off-course from 28R. Welke tools hebben je medewerkers nodig om het bedrijf de komende maanden zo goed mogelijk te laten draaien? The main (certified for credit) cameras here were the CMA-2600/2700 from CMC Electronics (I worked on these) and the Kollsman EVS I and II. The NTSB has stated that it wants faster incident reporting and considers recommending capturing the last 25 hours, an increase from two hours. As the pilots were slow to report the incident, the plane had made another flight and the cockpit voice recording was recorded over. For some, we use throttle and landing gear position and others we use speed and altitude above the landing airport. I'd assume like cameras used at sporting events the lens would be covered by a clear plastic film on a roll, which can be moved to get a clean section. They ruin other pilots' and crewmembers night vision. What is critical is that pilots follow their checklists and that 1 action would have prevented this happening despite the fact that the other systems could have warned about it. Based on the abstract I would say you're going to find out it came back down in under 30 minutes, and then "oops" they let the CVR be re-used, overwriting the recording anyway. EDDF (Frankfurt) RWY18 is only used for takeoffs and was causing nuisance alerts due to the way we search for the runway in front of the aircraft. BI News. [13], AC759 completed its go-around and landed without incident after the second approach. 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. We've run into similar issues while developing a related feature that helps pilots perform a stable approach. In this deviation, the pilots literally got lost. > The flight crew’s work schedule for the incident flight complied with the applicable Canadian flight time limitations and rest requirements; however, the flight and duty time and rest requirements for the captain (a company reserve pilot) would not have complied with US flight time limitations and rest requirements (14 CFR Part 117).