# Accident 20250913014449A: Cessna 172F, Lancaster, TX, September 13, 2025

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 13, 2025, 00:01 local time
- Place: Lancaster, TX
- Airport: Lancaster Regional Airport
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 32.5874° N, 96.7265° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.5874&lon=-96.7265&mi=10
- Aircraft: N7774A, registered now (https://openairdocs.org/aircraft/N7774A) (OpenAirDocs)
- Registry model: Cessna 172F (registry code 2072414, https://openairdocs.org/model/cessna-172f) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172F
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 220 total
- NTSB investigation: [NTSB CEN25LA377](https://openairdocs.org/ntsb/CEN25LA377) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20250913014449A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE PILOT STATED THAT HE ARRIVED AT THE AIRPORT THAT MORNING AROUND 6 AM FOR A TIME BUILDING FLIGHT WITH ANOTHER RATED PILOT WHO DID NOT SHOW UP. HE WAS ASKED TO FLY WITH TWO OTHER PILOTS TO KMXA TO PICK UP ANOTHER AIRPLANE. WHILE HE WAITED FOR THE OTHER PILOTS TO SHOW UP HE TOOK ANOTHER TIME BUILDING FLIGHT FOR ABOUT 1.9 HOURS WITH ANOTHER RATED PILOT. ON HIS RETURN THE OTHER TWO PILOTS WERE IN THE FRONT SEATS AND THE ACCIDENT PILOT WAS JUST A PASSENGER ON THE WAY TO KMXA, WHERE HE TOOK A NAP. THE ACCIDENT AIRPLANE STOPPED IN HOT SPRINGS, ARKANSAS FOR FUEL. AFTER ARRIVING THE ACCIDENT PILOT WAITED FOR THE TWO OTHER PILOTS TO PREFLIGHT AND TEST FLY THE OTHER AIRPLANE. THE ACCIDENT PILOT DEPARTED ABOUT 8:05 AND RAN OUT OF FUEL ABOUT 12 AM, 4 HOURS LATER. THE PILOT HAD USED AVARE FLIGHT PLANNING APP. THE PILOT STATED THAT HE WAS ON BASE LEG, THOUGHT HE WAS HIGH SO HE EXECUTED A RIGHT 270 TURN TO ALIGN WITH THE RUNWAY. THE ENGINE RAN ROUGH IN THE TURN, AND THE ENGINE QUIT DURING THE TURN AND DID NO RESTART WHEN HE WENT BACK TO WINGS LEVEL. THE PILOT ENDED UP SHORT OF THE RUNWAY BY 1000 AND HE RAN INTO THE OUTSIDE OF THE AIRPORT FENCE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN25LA377](https://openairdocs.org/ntsb/CEN25LA377), Sep 13, 2025: Cessna 172F (N7774A), Lancaster, TX, substantial damage. Probable cause: The pilot’s inadequate fuel planning and failure to monitor the fuel consumption which resulted in a total loss of engine power due to fuel exhaustion.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.