LAX94LA262 · Payne Foster GLASAIR
Payne Foster GLASAIR · Accident: loss of control in flight during landing
From Fresno Chandler Executive Airport (FCH) to Barstow Daggett Airport (DAG)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX94LA262
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
- General aviation
- 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
Payne Foster GLASAIR Possible conflict
- Aircraft type
- Payne Foster GLASAIR
- 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
- N250CH
- Operator
- Mcintosh, Richard Laverne · private individual
- Onboard fatalities
- Unknown
- Route
- From Fresno Chandler Executive Airport (FCH), Fresno, CATo Barstow Daggett Airport (DAG), 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 91: General Aviation
- 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
- Landing · aborted
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Directional control, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT COLLIDED WITH THE GROUND AND A PARKED AIRCRAFT OFF THE RIGHT SIDE OF RUNWAY 21 AFTER THE PILOT EXPERIENCED A GUST OF WIND DURING THE APPROACH. DURING THE ATTEMPTED GO-AROUND, THE AIRCRAFT VEERED ACROSS THE RUNWAY AND COLLIDED WITH ANOTHER PARKED AIRCRAFT THAT WAS BEING REFUELED. IN ADDITION TO THE GUST OF WIND, THE PILOT STATED TO AN FAA WITNESS THAT HE FORGOT ABOUT THE DENSITY ALTITUDE AND LEANING THE FUEL MIXTURE.
Probable cause
the pilot's loss of directional control during an attempted landing and subsequent go-around. Factors were the high-density altitude, inappropriate fuel leaning procedures, and the gust of wind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA262
- Event ID
- 20001206X01578
- Case number
- LAX94LA262
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- 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. 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: fcb7659a19c306870dfd5d81d792d33daa5d5799963f7c9709062a6b16e94824; retrieved 2026-09-21T22:36:16.271Z.