Piper PA-31-350 accident near North Las Vegas, Nevada, October 15, 1999
On October 15, 1999 at about 2:46 am local time, a Piper PA-31-350, registered N1024B, was destroyed in an accident near North Las Vegas, Nevada. It was a flight of an unrecorded kind under charter and air-taxi rules (Part 135). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 15, 1999 · about 2:46 am local time
- Place
- North Las Vegas, Nevada · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-31-350 · all PA-31-350s on the register
- Registration
- N1024B · registry record · serial 31-7652107
- Damage
- Destroyed
- Flight
- Flight of an unrecorded kind · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: airline transport pilot, flight instructor
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 2,103 hours in all; 250 in this make and model; 176 in the last 90 days; 40 in the last 30 days; 1,956 as pilot in command; 546 on instruments
- Medical certificate: Class 1 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 14,048 hours
- Last inspection: approved inspection programme, September 30, 1999; 26 hours since
- Maximum gross weight: 7,000 lb
- Seats: 2
- Landing gear: retractable
- Engine: Lycoming TIO-540-J2BD (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: VGT NV at 2:41 am
- Destination: SAC Sacramento CA
- Flight plan: IFR
- Runway 0
Weather at the time
- Light: night, dark
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 19°F (-7°C)
- Altimeter: 29.00 inHg
- Observation at 2:47 am from VGT, 11 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N1024B the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.