ASN Wikibase Occurrence # 44396
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Thursday 4 August 2005 |
| Time: | 02:06 |
| Type: |  Mitsubishi MU-2B-60 Marquise |
| Owner/operator: | Flight Line, Inc. |
| Registration: | N454MA |
| MSN: | 1535SA |
| Year of manufacture: | 1981 |
| Total airframe hrs: | 12575 hours |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Parker, CO -
 United States of America
|
| Phase: | Approach |
| Nature: | Unknown |
| Departure airport: | Salt Lake City, UT (SLC) |
| Denver, CO (APA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The commercial pilot was executing a precision instrument approach at night in instrument meteorological conditions when the airplane collided with terrain about four miles short of the runway. A review of air traffic control communications and radar data revealed the pilot was vectored onto the final approach course but never got established on the glide slope. Instead, he made a controlled descent below the glide slope as he proceeded toward the airport. When the airplane was five miles from the airport, a tower controller received an aural low altitude alert generated by the Minimum Safe Altitude Warning (MSAW) system. The tower controller immediately notified the pilot of his low altitude, but the airplane collided with terrain within seconds. Examination of the instrument approach system and onboard flight navigation equipment revealed no pre-mishap anomalies. A review of the MSAW adaptation parameters revealed that the tower controller would only have received an aural alarm for aircraft operating within 5 nm of the airport. However, the frequency change from the approach controller to the tower controller occurred when the airplane was about 10.7 miles from the airport, leaving a 5.7 mile segment where both controllers could receive visual alerts, but only the approach controller received an aural alarm. A tower controller does not utilize a radar display as a primary resource for managing air traffic. In 2004, the FAA changed a policy, which eliminated an approach controller's responsibility to inform a tower controller of a low altitude alert if the tower had MSAW capability. The approach controller thought the MSAW alarm parameter was set 10 miles from the airport, and not the 5 miles that existed at the time of the accident. Subsequent investigation revealed, that The FAA had improperly informed controllers to ensure they understood the alarm parameters for control towers in their area of responsibility. This led the approach controller to conclude that the airplane was no longer her responsibility once she handed it over to the tower controller. Plus, the tone of the approach controller's aural MSAW alarm was not sufficient in properly alerting her of the low altitude alert.
Probable Cause: The pilot’s failure to fly a stabilized instrument approach at night which resulted in controlled flight into terrain. Contributing factors were; the dark night, low clouds, the inadequate design and function of the airport facility’s Minimum Safe Altitude Warning System (MSAW), and the FAA’s inadequate procedure for updating information to ATC controllers.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20050810X01193&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 06-Dec-2017 10:50 | ASN Update Bot | Updated [Operator, Departure airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation