ERA25LA345 · Cessna 172 G
Cessna 172 G · Accident: loss of engine power (total) on approach
From Orlando Executive Airport (KORL) to an unrecorded destination
Event
- NTSB case
- ERA25LA345
- 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
- Ongoing
- 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 G
- 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
- N345QA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (KORL), Orlando, FLTo not recorded
- Aircraft age
- About 60 years (built 1965)
- 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
- Approach · VFR pattern final
- 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 engine power (total)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On September 13, 2025, about 0733 eastern daylight time, a Cessna 172G, N345QA, was substantially damaged when it was involved in an accident near Williston, Florida. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the flight departed Orlando Executive Airport (ORL), Orlando, Florida, about 0600 with 17 gallons of fuel onboard, overflew Cross City Airport (CTY), Cross City, Florida, and was scheduled to land at Williston Regional Airport (X60), Williston, Florida. About 1.5 hours after departure, while the airplane transitioned from the base leg to the final leg of the airport traffic pattern for runway 05 at X60, the engine experienced a momentary loss of power, followed shortly thereafter by a total loss of power. The pilot was unable to restore power to the engine and performed a forced landing to a field. During the landing roll, the nose landing gear collapsed, the airplane nosed over and came to rest in a grass field about 0.25-mile from the approach end of runway 05. The airplane sustained substantial damage to the fuselage and left wing strut. The airplane was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25LA345
- Event ID
- 20250915201000
- Case number
- ERA25LA345
- 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. 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: 754a40db0b411e7bccbe67f28b9dc084765181b005a996f2cb0b8cf730bed9cb; retrieved 2026-09-16T20:20:17.386Z.