WPR09LA307 · Gunnoe Velocity
Gunnoe Velocity · Accident: system/component malfunction/failure (non-power) during takeoff
From Livermore Municipal Airport (LVK) to Livermore Municipal Airport (LVK)
Event
- NTSB case
- WPR09LA307
- 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
Gunnoe Velocity
- Aircraft type
- Gunnoe VELOCITY
- 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
- N92VA
- Operator
- David Dent
- Onboard fatalities
- Unknown
- Route
- From Livermore Municipal Airport (LVK), Livermore, CATo Livermore Municipal Airport (LVK), Livermore, 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
- Takeoff · rejected takeoff
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The mechanic/pilot performed engine maintenance on the experimental airplane and was taking the airplane out for a high-speed taxi and check flight. He said that during the takeoff roll the right brake did not feel as he expected it to, and he decided to abort the takeoff. As the airplane exited the runway and proceeded onto the taxiway, the pilot activated the right brake to straighten the airplane when the right brake failed. The airplane began to spin and came to rest on an adjacent grassy area where the right brake ignited a fire burning the grass and the airplane. By the time the fire department arrived, the airplane's engine section, firewall, and part of the fuselage had been fire damaged. A postaccident inspection by a Federal Aviation Administration inspector revealed that the right brake caliper had been restricted by the wheel pant. This caused drag on the brake rotor allowing it to build up heat and eventually caused the fluid line to fail.
Probable cause
The failure of the right brake due to a restricted brake rotor and subsequent brake fluid line failure as a result of inadequate maintenance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA307
- Event ID
- 20090623X44116
- Case number
- WPR09LA307
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b429c54650ac02d216eeb3a44792f9c1af8e21349dd2f50406ec385220550729; retrieved 2026-09-15T11:33:05.197Z.