ERA25LA148 · Cessna 172 S
American Aviation Flight Academy Cessna 172 S · Accident: abnormal runway contact during landing
From Brooksville–Tampa Bay Regional Airport (BKV) to Brooksville–Tampa Bay Regional Airport (BKV)
Event
- NTSB case
- ERA25LA148
- 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 172 S
- 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
- N740SP
- Operator
- American Aviation Flight Academy
- Onboard fatalities
- Unknown
- Route
- From Brooksville–Tampa Bay Regional Airport (BKV), Brooksville, FLTo Brooksville–Tampa Bay Regional Airport (BKV), Brooksville, FL
- Aircraft age
- About 25 years (built 2000)
- 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
- 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
- Abnormal runway contact
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was on a solo instructional flight in the airport traffic pattern. She approached the runway and described that the airplane touched down on both main landing gear and that the nosewheel touched down almost immediately thereafter. The airplane then bounced three times, which each bounce being harder than the last. After the last bounce, the pilot taxied off the runway uneventfully. The underside of the airplane’s fuselage was substantially damaged during the accident sequence. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s improper landing flare, which resulted in a hard, bounced landing and substantial damage to the airplane’s fuselage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA148
- Event ID
- 20250320199882
- Case number
- ERA25LA148
- 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, 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: 5d28a2b5da93227eca7710299fee55c37746a31cb64af1e70da6cee7d4648499; retrieved 2026-09-16T19:44:52.818Z.