DEN07LA042 · Mino Kitfox 3
Mino Kitfox 3 · Accident: hard landing
From Fremont County Airport (1V6) to an unrecorded destination
Event
- NTSB case
- DEN07LA042
- 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
Mino Kitfox 3
- Aircraft type
- Mino KITFOX 3
- 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
- N928LM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fremont County Airport (1V6), Canon City, COTo 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The certificated flight instructor and the pilot/owner flew southeast of the airport to do air work. After 30 minutes, the airplane returned to the traffic pattern. The pilot/owner entered the traffic pattern on a left base leg for the runway, and the instructor pilot later commented, "Our turn to final was low, flat, at about 65 miles per hour with no flaps." He said that on final he reminded the pilot of the right crosswind, and to be sure that they touched down with no crab. The airplane touched down in a slight right crab and bounced. The instructor pilot said the stick was pushed forward, and they bounced again. On each bounce, the airplane continued to turn right. The left wingtip eventually scraped on the runway, the left main wheel axle fractured, and the airplane nosed over. Postaccident inspection of the airplane's systems disclosed no anomalies. The wind conditions at the time were 50 degrees off the runway heading at 3 knots.
Probable cause
The certificated flight instructor's failure to adequately supervise the dual student during the landing flare-touchdown, which resulted in a hard landing and a nose over. A factor associated with the accident is the dual student's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07LA042
- Event ID
- 20070103X00001
- Case number
- DEN07LA042
- 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, coordinates. 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: 42a341cd341b129062b19ad5129ca79ddc5c6927f9cf749ed31de29a7cf097e5; retrieved 2026-09-21T08:52:07.037Z.