LAX01LA161 · Taylor BANDIT
Taylor BANDIT · Accident: partial loss of engine power (mechanical failure) en route
From Yuba County Airport (MYV) to an unrecorded destination
Event
- NTSB case
- LAX01LA161
- 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
- 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
- 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
Taylor BANDIT
- Aircraft type
- Taylor BANDIT
- Category
- Gyroplane
- 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
- N8057T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yuba County Airport (MYV), Marysville, CATo not recorded
- 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 · climb to 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
- Partial loss of engine power (mechanical failure)
- 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 contamination
- 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
- Fluid, fuel › Contamination, water
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The experimental gyrocopter dropped back to the runway and caught fire following a loss of engine power during takeoff. The gyrocopter made a nose high takeoff. About 50 to 100 feet in the air, the engine sputtered and the gyrocopter fell straight back down to the runway. It burst into flames, and the pilot extricated himself from the wreckage. He fled the runway, on his own power with his clothes on fire, to a truck where medical personnel provided treatment. The gyrocopter had tapered fuel tanks that narrowed at the bottom. Fuel lines at the bottom of the tank went from the leading and trailing edge of the tank to the engine. The pilot used two plastic gas cans to fuel the gyrocopter. About 1/2 gallon of fuel remained in each can, and investigators discovered water in each can. The gas had been in the fuel cans when the pilot arrived at the airport. A third can that was full of fuel also had water in it.
Probable cause
The pilot performed an inadequate preflight inspection resulting in a loss of engine power at a low altitude because of water contamination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA161
- Event ID
- 20010508X00905
- Case number
- LAX01LA161
- 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: 2657b5faf0e0146d1df2f7e1c93b42e66dafffb40d25a9e81d01f455d10cde08; retrieved 2026-09-21T10:09:03.950Z.