20250913014449A

Accident · Substantial damage

FAA accident report · Cessna 172F · Lancaster, TX · September 13, 2025

Date
September 13, 2025 · 00:01 local
Place
Lancaster, TX
Airport
Lancaster Regional Airport
Phase of flight
Landing: Approach
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N7774A
NTSB investigation
NTSBCEN25LA377
Reported as
Cessna 172F
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
220 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.