MIA96LA087 · Marks KITFOX II
Marks KITFOX II · Accident: airframe, component or system failure during initial climb
From PFN to an unrecorded destination
Event
- NTSB case
- MIA96LA087
- 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
Marks KITFOX II
- Aircraft type
- Marks KITFOX
- 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
- N915PK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From PFNTo 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
- Initial climb
- 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
- Airframe, component or system failure
- 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) › Directional control, not maintained
- Pilot in command(cfi) › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After takeoff, the flight instructor (CFI) recognized that the airspeed indicator was inoperative. He elected to return to the airport and land on runway 32. During the landing, the airplane bounced, then drifted off the right side of the runway. The CFI then applied power to go-around, but the airplane collided with a ditch. The wind was reported to be from 220 degrees at 8 knots. Runway 23 was available for landing with nearly a direct headwind.
Probable cause
the pilot's improper recovery from a bounced landing, and his failure to maintain directional control of the airplane, which resulted in an inadvertent ground swerve and subsequent collision with a ditch. Factors relating to the accident were: failure of the airspeed indicator, the pilot's selection of the wrong runway for landing, and the crosswind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96LA087
- Event ID
- 20001208X05303
- Case number
- MIA96LA087
- 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: a97b9d734114473eab68159323ba2c7f9c0912fd092f1cbbb6b9a1ee264912f1; retrieved 2026-09-21T12:52:56.127Z.