# Accident 19991014031719A: Piper PA31350, North Las Vegas, NV, October 14, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: October 14, 1999, 19:46 local time - Place: North Las Vegas, NV - Damage: Destroyed - Phase of flight: To Init Climb(1st Pwr Reduct) - Operating rules: Air taxi and commuter (Part 135) - Operator: JIKA - Location: 36.2207° N, 115.1701° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=36.2207&lon=-115.1701&mi=10 - Aircraft: N1024B, a cancelled registration (https://openairdocs.org/deregistered/N1024B-2000-04-26) (OpenAirDocs) - Registry model: Piper PA-31-350 (registry code 7103110, https://openairdocs.org/model/piper-pa-31-350) (OpenAirDocs) - Reported make and model: PIPER PA31350 - Reported engine: LYC TIO540J2BD - People aboard: 1 - Fatal injuries: 1 - Pilot flight hours: 2,103 total, 250 in this make and model, 176 in the last 90 days - NTSB investigation: [NTSB LAX00FA014](https://openairdocs.org/ntsb/LAX00FA014) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19991014031719A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (.19) ON OCTOBER 14, 1999 AT 2000 HOURS PACIFIC DAYLIGHT TIME, A PIPER PA-31-350, N1024B, WAS DESTROYED BY IMPACT WITH MOUNTAINOUS TERRAIN, 11 MILES NORTH OF NORTH LAS VEGAS, NEVADA. THE AIRLINE TRANSPORT PILOT, THE SOLE OCCUPANT, WAS FATALLY INJURED. THE AIRCRAFT, TRANSPORTING BANKING PAPERWORK, WAS OPERATED UNDER THE PROVISIONS OF 14 CFR PART 135 BY AMERIFLIGHT, INC., AS FLIGHT 121, A NONSCHEDULED ON-DEMAND CARGO FLIGHT DESTINED FOR SACRAMENTO, CALIFORNIA. AN INSTRUMENT FLIGHT PLAN WAS FILED; HOWEVER, THE FLIGHT DEPARTED VFR FROM THE NORTH LAS VEGAS AIRPORT ABOUT 1952, AND WAS OPERATING UNDER VISUAL FLIGHT RULES AT THE TIME OF THE ACCIDENT. NIGHT, VISUAL METEOROLOGICAL CONDITIONS PREVAILED. ACCORDING TO FEDERAL AVIATION ADMINISTRATION FSDO PERSONNEL, BECAUSE HIS INSTRUMENT FLIGHT RELEASE WAS NOT AVAILABLE WHEN THE PILOT WAS READY FOR TAKEOFF, THE PILOT ELECTED TO DEPART UNDER VISUAL FLIGHT RULES WITH THE INTENTION OF PICKING UP THE FLIGHT'S INSTRUMENT CLEARANCE WHEN AIRBORNE. AFTER TAKEOFF, THE AIRCRAFT WAS OBSERVED TO DEPART THE AIRPORT AREA TO THE NORTH IN THE DIRECTION OF THE ACCIDENT SITE. THE NIGHT WAS REPORTED TO HAVE BEEN VERY DARK WITH ONLY A SMALL (NEW) MOON VISIBLE. THE PILOT WAS IN RADIO CONTACT WITH NELLIS APPROACH CONTROL AT THE TIME RADIO AND RADAR CONTACT WAS LOST NEAR THE ACCIDENT SITE. THE AIRCRAFT IMPACTED ON A LARGE BOULDER ON THE SOUTH FACE OF GASS PEAK AT THE 5,200-FOOT (MSL) LEVEL. THE SITE IS ON A ROCKY, ARID SLOPE ABOUT 40 DEGREES. THERE WAS A POST IMPACT FIRE. (.4)ON OCTOBER 4, 1999, AT 1946 HOURS PDT, A PIPER PA-31-350, N1024B, WAS DESTROYED BY IMPATCH WITH MOUNTAINOUS TERRAIN, 11 MILES NORHT OF NORTH LAS VEGAS, NEVADA. THE AIRLINE TRANSPORT PILOT, THE SOLE OCCUPANT WAS FATALLY INJURED. THE AIRCRA, TRANSPORT BANKING PAPERWORK, WAS OPERATED UNDER THE PROVISIONS OF 14 CFR PART 135 BY AMERIFLIGHT,INC., AS FLIGHT 121, A NONSCHEDULED ON-DEMAND CARGO FLIGHT DESTINED FOR SACRAMENTO, CALIFORNIA. AN INSTRUMENT FLIGHT PLAN WAS FILED; HOWEVER, THE FLIGHT DEPARTED VFR FROM THE NORHT LAS VEGAS AIRPORT AT 1941, AND WAS OPERATING UNDER FLIGHT RULES AT THE TIME OF HT ACCIDENT. NIGHT VISUAL METEOROLOGICAL CONDITIONS PREVAILED. THE OPERATOR REPORTED THAT THE OUTBOUND FREIGHT, APPROXIMATELY 300 POUNDS OF BANK PAPERWORK, ARRIVED AT THE NORTH LAS VEGAS AIRPORT ABOUT ONE HOUR LATE AND THE FLIGHT WAS DEPARTING BEHIND SCHEDULE. BECAUSE HIS INSTRUMENT FLIGHT RELEASE WAS NOT AVAILABLE WHEN HE WAS READY FOR TAKEOFF, THE PILOT ELECTED TO DEPART UNDER VISUAL FLIGHT RULES WITH THE INTENTION OF PICKING UP THE FLIGHT'S INSTRUMENT CLEARANCE WHEN AIRBORNE. BEFORE ISSUING TAKEOFF CLEARANCE, NORHT LAS VEGAS AIR TRAFFIC CONTROL TOWER INSTRUCTED THE PILOT TO RESET HIS TRANSPONDER TO A VFR CODE AND ISSUED A RECOMMENDED HEADING AFTER TAKEOFF OF 340 DEGREES. AFTER TAKEOFF ON RUNWAY 7, THE AIRCRAFT WAS OBSERVED TO TURN LEFT AND DEPART THE AIRPORT AREA TO THE NORTH IN THE DIRECTION OF THE ACCIDENT SITE. THE PILOT WAS IN RADIO AND RADAR CONTACT WITH NELLIS APPROACH CONTROL AT THE TIME RADAR CONTACT WAS LOST NEAR THE ACCIDENT SITE. LOCAL LAW ENFORCEMENT PILOTS, PATROLLING THE CITY IN A HELICOPTER, REPORTED THAT THE NIGHT WAS VERY DARK WITH ONLY A SMALL NEW MOON VISIBLE TO THE SOUTHWEST. GASS PEAK AND THE ADJACENT RIDGELINE WERE NOT VISIBLE IN THE NIGHT SKY. AS THEY WERE PATROLLING, THEY SAW THE BRIGHT FLASH OF THE FIRE WHEN THE AIRCRAFT IMPACTED THE MOUNTAIN AND PROCEEDED TO THE LOCATION. THEIR HELICOPTER WAS EQUIPPED WITH A FLIR (FORWARD LOOKING INFRARED SENSOR) WHICH THEY EMP LOYED TO LOCATE THE RIDGELINE. (-23)AIRCRAFT DEPARTED NORTH LAS VEGAS AIRPORT (VGT) AT APPROX 1941 LOCAL ENROUTE TO SACRAMENTO EXECUTIVE AIRPORT (SAC). AFTER TAKEOFF PILOT CLIMBED AND TURNED NORTH TO A SUGGESTED HEADING OF 340 AND CONTACTED NELLIS AFB CONTROL AT 1942 HRS LOCAL. NELLIS AFB CONFIRMED RADAR CONTACT AT 1944 HRS LOCAL NELLIS AFB LOST RADAR CONTACT WITH AMFLIGHT 121 AND RECEIVED CALLS FROM 2 AIRCRAFT WHO HAD WITNESSED A LARGE BRIGHT FLASH TO THE NORTHWEST IN THE AREA OF GASS PEAK IN THE LAS VEGAS RANGE. METRO LAS VEGAS POLICE HELICOPTER ARRIVED ONSCENE AT APPROX 1957 HRS LOCAL AND CONFIRMED AIRCRAFT HAD CRASHED AND WAS CONSUMED BY POST IMPACT FIRE AT AN ELEVATION OF APPROX 5,2000 FT MSL. PILOT, THE SOLE OCCUPANT WAS FATALLY INJURED. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX00FA014](https://openairdocs.org/ntsb/LAX00FA014), Oct 15, 1999: Piper PA-31-350 (N1024B), North Las Vegas, NV, destroyed, 1 fatal. 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… ## Other reports on N1024B (2) Matched to the same aircraft by N-number and date. - [Incident 19851018060049I](https://openairdocs.org/incident/19851018060049I), Oct 18, 1985: Piper PA31350 (N1024B), Fresno, CA. Turbocharger oil seal and bearing deteriorated. Left engine was smoking on final. Normal landing with no damage. - [Incident 19830305016409I](https://openairdocs.org/incident/19830305016409I), Mar 5, 1983: Piper PA31350 (N1024B), Pensacola, FL, Minor damage. #4 Cylinder top rod bolt broke causing the bottom bolt to twist and break. Rod bolts #3 cylinder ripped out. From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.