MIA05LA037 · Cessna 172N
Avion Jet Center Cessna 172N · Accident: airframe, component or system failure during landing
From Lakeland Linder International Airport (KLAL) to Orlando Sanford International Airport (KSFB)
Event
- NTSB case
- MIA05LA037
- 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
- N8077E
- Operator
- Avion Jet Center
- Onboard fatalities
- Unknown
- Route
- From Lakeland Linder International Airport (KLAL), Lakeland, FLTo Orlando Sanford International Airport (KSFB), Sanford, 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
- 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 › 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 while on final approach to runway 9L when the flight was approximately 25 feet, he manipulated the throttle, but it appeared the throttle was stuck in a position which was insufficient to perform a go-around. The airplane contacted the runway causing the emergency locator transmitter (ELT) to activate. The pilot advised air traffic control of the ELT activation and taxied the airplane to the ramp where he secured the airplane. He reported the ELT activation on the aircraft discrepancy log sheet. The post accident inspection of the aircraft was conducted by Avion Aviation Maintenance on November 9, 2004, without FAA or NTSB oversight. The inspection consisted of a visual engine inspection, and freedom of movement of the throttle control system. The throttle and mixture controls were found free and smooth and no defects were noted.
Probable cause
The improper flare by the pilot in command resulting in a hard landing, Restricted movement of the throttle was a contributing factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05LA037
- Event ID
- 20041208X01943
- Case number
- MIA05LA037
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-11-09.
- API snapshot SHA-256: 5648cb2234db778d0c87ea02c396c1d38d69d9775af2208f5e5750f55dbd1fc8; retrieved 2026-09-22T06:31:52.694Z.