ERA24LA270 · Cessna 172 M
Cessna 172 M · Accident: loss of control on ground during landing
From Brooksville–Tampa Bay Regional Airport (BKV) to an unrecorded destination
Event
- NTSB case
- ERA24LA270
- 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
Cessna 172 M
- 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
- N72CM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brooksville–Tampa Bay Regional Airport (BKV), Brooksville, FLTo not recorded
- Aircraft age
- About 49 years (built 1975)
- 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 · landing roll
- Defining eventThe 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
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 was attempting to land and noted that the airplane seemed to be flying “fast.” She described that while she believed that the wind conditions were favoring the runway selected for landing, she also noted that a gusting crosswind was present. During the landing, when she reached to adjust the flap setting, she inadvertently increased the throttle. She responded by applying braking, but the airplane ultimately departed the end of the runway and impacted trees. The airplane sustained substantial damage to both wings and the fuselage. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation, and that instead of landing at the accident airport, she should have diverted to an airport with a longer runway that was more oriented into the wind.
Probable cause
The pilot’s inadvertent throttle input during landing which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA270
- Event ID
- 20240621194513
- Case number
- ERA24LA270
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 517a01d7c26ea0814411261d7df833c9c268c08f6a676666379c66567e985ac6; retrieved 2026-09-16T18:56:45.406Z.