WPR25LA157 · Cirrus Design Corp SR22T
Truongton Aviation Cirrus Design Corp SR22T · Accident: runway excursion during landing
From Fullerton Municipal Airport (KFUL) to Fullerton Municipal Airport (KFUL)
Event
- NTSB case
- WPR25LA157
- 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
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
- N415DG
- Operator
- Truongton Aviation
- Onboard fatalities
- Unknown
- Route
- From Fullerton Municipal Airport (KFUL), Fullerton, CATo Fullerton Municipal Airport (KFUL), Fullerton, CA
- Aircraft age
- About 12 years (built 2013)
- 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
- Runway excursion
- 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 of the airplane reported that he was conducting a 180° power-off approach and landing. While landing on the 3,121 ft long runway, the airplane touched down about halfway down the runway. The pilot was unable to stop the airplane within the available runway length, and the airplane exited the departure end of the runway and struck a grassy berm, which resulted in the airplane’s nose gear collapse, and substantial damage to the firewall. The pilot initially reported that the brake system did not function as they expected; however, a brake system examination did not reveal any preaccident mechanical failures or malfunctions that would have precluded normal operation.
Probable cause
The pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA157
- Event ID
- 20250519200175
- Case number
- WPR25LA157
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-04-25.
- API snapshot SHA-256: ae0e2d985b2bef1fafaec3174a7a59e879bc86eebd83993fd09f238c4f4b30c5; retrieved 2026-09-16T19:53:23.786Z.