CEN12LA593 · Mudge RAY KIT FOX 5
Mudge RAY KIT FOX 5 · Accident: loss of control on ground during landing
From 419 · Bowling Green, OH to 419 · Bowling Green, OH
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN12LA593
- 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
Mudge RAY KIT FOX 5
- Aircraft type
- Mudge Ray KIT FOX 5
- 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
- N84KF
- Operator
- Daniel Walker
- Onboard fatalities
- Unknown
- Route Possible conflict
- From 419 · Bowling Green, OHTo 419 · Bowling Green, OH
- 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 · landing roll
- 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor was getting the pilot familiarized in his new tail wheel-equipped airplane. A week before the accident, the flight instructor and the pilot flew the airplane and the pilot made several uneventful landings even though the instructor noted that it was difficult to apply pressure on the rudder pedals without engaging the brakes. On the day of the accident, the pilot made two uneventful landings on a hard-surface runway before landing on grass due to a wind shift. The pilot's first grass landing was uneventful. However, on the second landing, the pilot applied too much brake pressure and the airplane nosed over. The flight instructor said the accident happened so fast that he did not have enough time to tell the pilot to get off the brakes.
Probable cause
The pilot receiving instruction's excessive braking during the landing roll, which resulted in a loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA593
- Event ID
- 20120830X71801
- Case number
- CEN12LA593
- 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: 7f7383967c8266704129f3409f597fbc2330f99db5ac2879b6ea704092874c30; retrieved 2026-09-15T19:36:13.092Z.