North Las Vegas – Sacramento
Flight / Schedule
North Las Vegas – Sacramento
Aircraft
Piper PA-31-350 Navajo ChieftainRegistration
N1024B
MSN
31-7652107
Year of Manufacture
1976
Operator
AmeriflightDate
October 14, 1999 at 07:46 PM
Type
CRASHFlight Type
Cargo
Flight Phase
Flight
Crash Site
Mountains
Crash Location
Gass Peak Nevada
Region
North America • United States of America
Coordinates
36.4005°, -115.1804°
Crash Cause
Human factor
Narrative Report
On October 14, 1999 at 07:46 PM, North Las Vegas – Sacramento experienced a crash involving Piper PA-31-350 Navajo Chieftain, operated by Ameriflight, with the event recorded near Gass Peak Nevada.
The flight was categorized as cargo and the reported phase was flight at a mountains crash site.
1 people were known to be on board, 1 fatalities were recorded, 0 survivors were identified or estimated. This corresponds to an estimated fatality rate of 100.0%.
Crew on board: 1, crew fatalities: 1, passengers on board: 0, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. 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.
Aircraft reference details include registration N1024B, MSN 31-7652107, year of manufacture 1976.
Geospatial coordinates for this crash are approximately 36.4005°, -115.1804°.
Fatalities
Total
1
Crew
1
Passengers
0
Other
0
Crash Summary
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.
Cause: Human factor
Occupants & Outcome
Crew On Board
1
Passengers On Board
0
Estimated Survivors
0
Fatality Rate
100.0%
Known people on board: 1
Operational Details
Schedule / Flight
North Las Vegas – Sacramento
Operator
AmeriflightFlight Type
Cargo
Flight Phase
Flight
Crash Site
Mountains
Region / Country
North America • United States of America
Aircraft Details
Aircraft
Piper PA-31-350 Navajo ChieftainRegistration
N1024B
MSN
31-7652107
Year of Manufacture
1976
