USAir Flight 499
From Wikipedia, the free encyclopedia
Summary | |
---|---|
Date | February 21, 1986[1] |
Type | Overrun |
Site | Erie International Airport |
Passengers | 19 |
Crew | 4 |
Injuries | 1 |
Fatalities | 0 |
Survivors | 23 |
Aircraft type | McDonnell Douglas DC-9-31 |
Operator | USAir |
Tail number | N961VJ |
USAir Flight 499 was scheduled to be flown from Toronto, Canada to Pittsburgh, Pennsylvania, with a scheduled stop en route in Erie, Pennsylvania, on February 21, 1986. The National Transportation Safety Board (NTSB) later reported that in Toronto, before takeoff, the flight crew discussed the weather reports, and the captain commented that the weather conditions were "not too good".[2] However, the crew decided to proceed with the flight anyway, and determined that their fuel supply was adequate to complete the flight for the weather conditions in Erie. At 4:00 a.m. EST, at Erie International Airport, a snowplow operator had begun to clear the runways, including Runway 06-24, the runway that Flight 499 was scheduled to land on.[3] The operator subsequently stated that the snow was "wet". At 5:45 a.m. EST, filing the first Field Condition Report of the day, he stated that braking conditions were poor. Around 35 minutes later, at 6:20 a.m. EST, after filing the first Field Condition Report, the snowplow operator stopped plowing, anticipating the arrival of Flight 499. He later checked braking conditions on the runway again, at 7:15 a.m. EST, using a James Brake Decelerometer installed in a pickup truck, and reported that braking conditions were fair to poor. At around 7:45 a.m. EST, a Beechcraft King Air landed on the runway, and reported to air traffic control that braking action was poor.[3] The King Air pilot observed that there was 1-2 inches of snow on the runway, with no visible bare spots on the runway. Due to visibility and tailwind concerns, Erie Operations directed the dispatcher to advise Flight 499 to proceed to Pittsburgh without stopping at Erie.[3]
However, after further discussion, the dispatcher advised Erie Operations to report to Flight 499, and tell them to make one approach, and if that approach was unsuccessful, then proceed to Pittsburgh. At 8:59 a.m. EST,[4] Flight 499 attempted to land on Runway 24 at Erie International Airport. However, the NTSB reported that, although the touchdown was steady, the autospoilers failed to deploy. It was later confirmed that the captain attempted to deploy the autospoilers manually.[5] The airplane started to drift slowly to the left, and eventually slid off the runway. The NTSB later reported that the airplane ran over a runway end identifier light, struck a chain-link fence, and finally came to a halt about 180 feet away from and 20 feet below the runway's end.[5] One passenger was reported to have bumped her head during the overrun, but there were no other injuries reported.[5]
The NTSB discovered that USAir policy prohibits landing at Runway 24 at Erie International Airport while there is any tailwind. The NTSB also reported that the dispatcher fulfilled his duties.[6] After investigating the case, the NTSB reported that the cause of the crash was due to an improper planning and decision on the part of the pilot-in-command,[7] referring to the decision to land at the airport despite reports. It also reported that a go-around was not performed by the pilot-in-command, another reason it lists as a probable cause of the accident.[7]
[edit] See also
[edit] References and notes
- ^ Note that the original NTSB report marks the date as February 21, 1966. However, the correct date of the accident is February 21, 1986, as verified
- ^ Aircraft Accident/Incident Summary Reports (PDF) p. 40. National Transportation Safety Board.
- ^ a b c Aircraft Accident/Incident Summary Reports (PDF) p. 41. National Transportation Safety Board.
- ^ Again, the original NTSB report marks 6:59 a.m., instead of 8:59 a.m. However, the only way it would be possible, based on other times given in the report, is if the time was 8:59 a.m., not 6:59 a.m. It also uses 8:59 a.m. later in the report, making this the only logical possible time.
- ^ a b c Aircraft Accident/Incident Summary Reports (PDF) p. 43. National Transportation Safety Board.
- ^ Aircraft Accident/Incident Summary Reports (PDF) p. 46. National Transportation Safety Board.
- ^ a b NTSB Brief Summary of the Incident