CEN25LA189 · Cirrus Design Corp SR22T
Pro Ag Aviation Cirrus Design Corp SR22T · Accident: hard landing
From Faribault Municipal Airport-Liz Wall Strohfus Field (FBL) to an unrecorded destination
Event
- NTSB case
- CEN25LA189
- 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
- Event fatalities
- Unknown
- 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
Cirrus Design Corp SR22T
- Aircraft type
- Cirrus SR22
- 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
- N202FD
- Operator
- Pro Ag Aviation
- Onboard fatalities
- Unknown
- Route
- From Faribault Municipal Airport-Liz Wall Strohfus Field (FBL), Faribault, MNTo not recorded
- Aircraft age
- Built the same year (2025)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- 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 reported that on his first landing attempt the airplane touched down with excessive force and he executed a go-around. On the pilot’s second attempt the airplane again landed with excessive force, but he thought he could still land the airplane. The airplane porpoised, nosed forward, and struck the propeller on the runway. The pilot reported that the airplane sustained damage to the propeller, nose landing gear, left wing, and firewall. Photographs of the airplane after the accident showed substantial damage to the firewall. The pilot reported no preimpact mechanical failures or malfunctions that would have precluded normal operation.
Probable cause
The pilot’s improper landing flare which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA189
- Event ID
- 20250528200229
- Case number
- CEN25LA189
- 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: 9b021b79d5467ef205dba704bb6ef2bbf63353191744a26fd9f56221b2f8e7f3; retrieved 2026-09-16T19:55:14.606Z.