Ameriflight Piper PA-32R-300 accident
Piper PA-32R-300 · Accident: in flight collision with terrain/water en route
From Inyokern Airport (IYK) to Eastern Sierra Regional Airport (BIH)
Event
- NTSB case
- LAX04FA102
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-32R-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N8701E
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From Inyokern Airport (IYK), Inyokern, CATo Eastern Sierra Regional Airport (BIH), Bishop, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During cruise flight on a clear VFR day, the airplane collided with top of a ridgeline in a wing and nose level attitude. A post-impact fire destroyed the fuselage and forward cockpit areas. The pilot's normal workweek was Monday through Friday. Family members said he would leave his residence each day around 0530 in order to report to operations at the required 0600 time, and return home around 2030 each evening at the conclusion of his shift; going to bed around 2300. A captain who had flown with the accident pilot during the pilot's initial training (the accident pilot was observing en route procedures) indicated that during two flights, both from Inyokern to Bishop (the general area of the accident), the accident pilot had fallen asleep. The first time the accident pilot stated that he was tired and asked if it would be okay if he slept for a little bit. The second time, he just went to sleep. Both naps lasted between 20-30 minutes. A dispatcher working the night shift on January 20th reported that the accident pilot was 2.5 hours late returning to Burbank. The pilot was scheduled to be back at 1700, but had encountered adverse weather at Mammoth and did not return to the company base until 1930. The dispatcher reported that the accident pilot looked "beat up," like he had had a rough flight. According to the operator, the airplane was equipped with an autopilot. Due to the thermal damage to the airplane, the autopilot was not recovered. No discrepancies were noted with the airframe or engine that would have precluded normal operation.
Probable cause
failure of the pilot to maintain clearance with mountainous terrain for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA102
- Event ID
- 20040203X00155
- Case number
- LAX04FA102
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e55506027332718e0e29bf43a3ffb161e4c63730e0a829bf5629bb6db003a2d3; retrieved 2026-09-18T13:01:14.118Z.
- The NTSB's operator name is blank for N8701E; the operator shown is the name the NTSB's other records give its FAA operator code, JIKA.