MIA06CA101 · Cessna 172N
ADF Airways Cessna 172N · Accident: hard landing
From Miami Executive Airport (KTMB) to Miami Executive Airport (KTMB)
Event
- NTSB case
- MIA06CA101
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N738DW
- Operator
- ADF Airways
- Onboard fatalities
- Unknown
- Route
- From Miami Executive Airport (KTMB), Miami, FLTo Miami Executive Airport (KTMB), Miami, FL
- 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 › Flare, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that approximately 20 minutes after takeoff he radioed the Kendall-Tamiami Executive Airport Air Traffic Control Tower and requested touch-and-go landings. He reported having difficulty with the aircraft's radio and was cleared for a full stop landing on runway 9R. He further reported,''...the landing seemed normal; the main wheels touch down, but then as I noticed the yoke not releasing from the flare, the aircraft starts to balloon, I add a little power and attempt to land but the yoke was stiff." The airplane ballooned "...a couple of times, hitting the ground hard until I finally stopped." He taxied the airplane to the ramp and secured it where he again noticed the elevator control still stiff. Postaccident examination of the airplane by an airframe and powerplant mechanic revealed impact damage to the firewall, and the control yoke was displaced up and was in contact with an instrument panel support bracket. Examination of the elevator flight control system revealed no evidence of preimpact failure or malfunction.
Probable cause
The improper flare by the pilot resulting in a hard landing and substantial damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA06CA101
- Event ID
- 20060628X00842
- Case number
- MIA06CA101
- 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: 174e074c099fedae06113c1dbe4101c80528d2a4ff839f31a0cb0929d8b39942; retrieved 2026-09-22T04:57:15.947Z.