LAX00LA238 · Ward SIDEWINDER
Ward SIDEWINDER · Accident: total loss of engine power (non-mechanical) en route
From Red Bluff Municipal Airport (RBL) to Fresno Chandler Executive Airport (FCH)
Event
- NTSB case
- LAX00LA238
- 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
Ward SIDEWINDER
- Aircraft type
- Ward SIDEWINDER
- 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
- N4119Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Red Bluff Municipal Airport (RBL), Red Bluff, CATo Fresno Chandler Executive Airport (FCH), Fresno, 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
- En route · descent
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion; Stall
- 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 › Flight to new destination, delayed
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › Short field landing/procedure, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
This was a cross-country flight from Oregon to California with two en route stops planned to refuel. The flight departed at 0730, with refueling stops along the way. A departure time of 1120 was made from the second airport. The pilot indicated that the airplane had a fuel capacity of 20 gallons and a burn rate of 8 gallons per hour, approximately 2 1/2 to 3 hours of flight, and was not equipped with flaps. After arrival at the destination airport, at 1320, he made three attempts to land. Due to winds and a high temperature he was unable to land. On all three attempts, he landed approximately halfway down the runway, and did not feel there was enough room to safely come to a stop. He departed the airport at 1345 to attempt a landing at an airport approximately 20 nmi from his current position; passing by an airport 5 miles from his current location because he did not have a transponder onboard the airplane and did not want to enter Class C airspace without it. Approximately 6 miles from the airport the engine quit, and the pilot started looking for a place to make an emergency landing.
Probable cause
The pilot's inadequate short field landing procedure and his delayed decision to proceed to an alternate destination, which resulted in fuel exhaustion and a subsequent hard landing during the emergency descent.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA238
- Event ID
- 20001212X21274
- Case number
- LAX00LA238
- 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: 72d79ec8c196256ac995183d122f042239ee6a7379fbb5cec4e0661b7d91e9cf; retrieved 2026-09-22T12:47:32.079Z.