MIA03LA114 · Cessna 172E
Cessna 172E · Accident: in flight collision with terrain/water en route
From Earle Airpark (13FA) to None
Event
- NTSB case
- MIA03LA114
- 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 172E
- 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
- N817T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Earle Airpark (13FA), Hastings, FLTo None
- 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
- En route · descent
- 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
- In flight collision with terrain/water
- 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 › Aircraft control, not maintained
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 he installed the transponder and was taxiing to check whether it was operative. While taxiing, he lost directional control of the airplane and after observing a ditch, he applied power to clear the ditch. The airplane cleared the ditch and he then reduced power and the airplane descended and came to rest in brush. As a result of the landing in brush, damage to the airplane consisted of the shearing of the right main landing gear. Additionally, skin inboard of the right main landing gear was damaged. The airplane was dropped during recovery causing additional damage. The pilot did not initially advise the NTSB there was a passenger on board the airplane. The pilot later reported in writing that at no time did the airplane attain liftoff speed, and that a wind gust caused a ground loop. The pilot-rated passenger who is a FAA certificated airframe and powerplant mechanic verbally reported that he was onboard the airplane to check whether the installed transponder was operational. He boarded the airplane, donned a headset to communicate with the pilot, and by habit buckled his seatbelt though there was no intent for flight. He was not paying attention to what was occurring, and reported he did not know how fast the pilot was taxiing or whether engine power was increased at any point while he was on the airplane. He was looking at a sectional for a planned future flight, and reported the pilot advised him with words to the effect that the airplane was going to crash. He looked up, saw trees, braced for impact, and the airplane mushed into trees. He exited the airplane using the left door, as the right door was blocked by obstructions and the way the airplane was resting. He further stated the airplane was traveling westbound from the pilot's hangar towards the runway, and the wind was from the west or southwest at 11-13 miles per hour (mph). He also stated that the airplane was equipped with a short takeoff and landing (STOL) kit and could become airborne at 40-45 mph. A pilot-rated witness reported that he heard engine power applied and observed the airplane flying westbound, climbing steeply to an estimated 100 feet above ground level. The airplane then banked abruptly to the left about 45 degrees angle of bank, and he then heard engine power reduced. The airplane then settled to the ground where he heard two impacts. He did not hear any discrepancy related to the engine, and reported it sounded strong and steady, with no sputtering. He reported that the pilot's house is located approximately 400-450 feet east of the north/south oriented runway. The pilot provided a statement from an individual who reported hearing an engine start, followed by running at idle speed. He then heard the engine rpm increase to what he thought would be for taxiing. He then heard the engine sound increase to a very high sound for 4-5 seconds followed by decreasing to a low rpm sound. He then heard a, "thump, thump, thump" sound and drove to the runway where he observed the pilot and passenger walking from the airplane that was located in weeds west of the runway approximately 25 feet. That person reported seeing ground scars in the, "soft sandy earth leading to the aircraft." Review of the FAA Flight Training Handbook revealed that with respect to taxiing, the taxi speed should be such that when throttle is closed, the airplane can be stopped promptly.
Probable cause
The failure of the pilot to maintain control of the airplane resulting in in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA114
- Event ID
- 20030610X00831
- Case number
- MIA03LA114
- 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: 638109c305dd96d668f6d2eadce0e2d1a771c65580ba535baf69d19ab1792171; retrieved 2026-09-22T09:15:24.567Z.