ASN Wikibase Occurrence # 35299
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 14 October 1999 |
| Time: | 19:46 LT |
| Type: |  Piper PA-31-350 Chieftain |
| Owner/operator: | Ameriflight, Inc. |
| Registration: | N1024B |
| MSN: | 31-7652107 |
| Year of manufacture: | 1976 |
| Total airframe hrs: | 14048 hours |
| Engine model: | Lycoming TIO-540-J2BD |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Gass Peak, Sheep Mountains, 11 miles North of North Las Vegas, Nevada -
 United States of America
|
| Phase: | En route |
| Nature: | Unknown |
| Departure airport: | , NV (KVGT) |
| Sacramento, CA (SAC | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The airplane collided with mountainous terrain during climb to cruise on a night departure. The pilot of the on-demand cargo flight was brought in off reserve to replace the scheduled pilot who was ill. The flight was behind schedule because the cargo was late. When the instrument flight release created further delay, the pilot opted to depart into the clear, dark night under visual flight rules (VFR) with the intention of picking up his instrument clearance when airborne. When clearing the flight for takeoff, the tower controller issued a suggested heading of 340 degrees, which headed the aircraft toward mountainous terrain 11 miles north of the airport. The purpose of the suggested heading was never stated to the pilot as required by FAA Order 7110.65L. After a frequency change to radar departure control, the controller asked the pilot 'are you direct [the initial (route) fix] at this time?' and the pilot replied, 'we can go ahead and we'll go direct [the initial fix].' A turn toward the initial fix would have headed the aircraft away from high terrain. The controller then diverted his attention to servicing another VFR aircraft and the accident aircraft continued to fly heading 340 degrees until impacting the mountain. ATC personnel said the 340-degree heading was routinely issued to departing aircraft to avoid them entering Class B airspace 3 miles from the airport. The approach control supervisor said this flight departs daily, often VFR, and routinely turns toward the initial fix, avoiding mountainous terrain. When the pilot said that he would go to the initial fix, the controller expected him to turn away from the terrain. Minimum Safe Altitude Warning (MSAW) was not enabled for the flight because the original, instrument flight plan did not route the aircraft through this approach control's airspace and the controller had not had time to manually enter the flight data. High terrain was not displayed on the controller's radar display and no safety alert was issued.
Probable Cause: The failure of the pilot-in-command to maintain separation from terrain while operating under visual flight rules. Contributing factors were the improper issuance of a suggested heading by air traffic control personnel, inadequate flight progress monitoring by radar departure control personnel, and failure of the radar controller to identify a hazardous condition and issue a safety alert.
Accident investigation:
 |
|
Sources:
NTSB LAX00FA014
FAA register: NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001212X19974&key=1
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=1024B
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 24-Oct-2008 10:30 | ASN archive | Added |
| 25-Jun-2015 20:06 | Dr. John Smith | Updated [Time, Location, Nature, Departure airport, Destination airport, Source, Narrative] |
| 21-Dec-2016 19:22 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 16-Oct-2017 14:01 | Dr. John Smith | Updated [Time, Operator, Source, Narrative] |
| 14-Dec-2017 09:40 | ASN Update Bot | Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative] |
| 07-Apr-2024 17:24 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
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