FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26FA043 · Cessna 172M

10 Nov 2025 · Poleta, CA, United States

Cessna 172M · Accident en route

From Eastern Sierra Regional Airport (BIH) to North Las Vegas Airport (VGT)

Report a problem

Event

NTSB case
WPR26FA043
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
2 · 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

Cessna 172M

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
N13221
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eastern Sierra Regional Airport (BIH), Bishop, CATo North Las Vegas Airport (VGT), North Las Vegas, NV
Aircraft age
About 52 years (built 1973)
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
En route
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
Unknown or undetermined
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On November 10, 2025, at about 1515 Pacific standard time, Cessna 172M, N13221, was substantially damaged when it was involved in an accident near Poleta, California. A pilot-rated passenger and a passenger were fatally injured, and the pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. On the day of the accident, the pilot rented the airplane from a flight school at North Las Vegas Airport (VGT), Las Vegas, Nevada. According to the flight school, the airplane was fueled to capacity. ADS-B data indicated the airplane subsequently departed for a flight to Bishop Airport (BIH), Bishop, California, at 1159. At 1416, the airplane arrived at BIH. The pilot purchased about 10 gallons of fuel from the self-serve fuel pump. The airplane subsequently departed from runway 17 at 1505. The airplane began a climbing left turn to the southeast and approached a mountain range with terrain elevations that reached up to about 9,000 ft msl. (See Figure 1). The last ADS-B return was recorded at 1514 and captured the airplane at 6,850 ft msl.

Figure 1: Flight path of the accident airplane.

Figure 2: The ADS-B flight track, shown in red, overlaid on a topographic map of the canyon. When the airplane failed to return to VGT, the flight school contacted local law enforcement, who subsequently contacted the FAA. The FAA then issued an Alert Notice (ALNOT). The airplane was located the day after the accident at about 0600. The accident site was located in the east end of a canyon about 9.6 miles southeast of BIH, and about 1.3 miles northeast of the last ADS-B return. The terrain elevation at the bottom of the canyon rose from 4,400 ft msl near the opening (which faced west) and reached about 7,600 ft msl near the east end of the canyon. The airplane came to rest at an altitude of about 7,000 ft msl on a shale-covered slope on the north face of the canyon. The wreckage lay on a heading of about 077° magnetic. The airplane was surrounded by fragments of interior plastics and the windows. The main cabin doors had separated and came to rest downslope of the main wreckage. (See Figure 3).

Figure 3: A view of the main wreckage, with the camera facing southwest. The wings, empennage, and engine remained attached to the fuselage. Several gallons of fuel were present in each fuel tank. Upon visual examination, the engine exhibited no indications of internal catastrophic engine failure. The propeller remained attached to the crankshaft flange. One propeller blade had separated and was found imbedded in the soil near the main wreckage. Visual examination of the propeller blades revealed leading edge chipping, S-bending, and chordwise striations. The aircraft was retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR26FA043
Event ID
20251111201989
Case number
WPR26FA043
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. 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: e02cc07a6845eec5b4c646aebb5ccc8ad02d32193f359ccaf685a265e94ae5bc; retrieved 2026-09-15T09:10:59.870Z.