WPR14FA078 · Cessna 172K P
Cessna 172K P · Accident: loss of control in flight while maneuvering
From Tehachapi Municipal Airport (KTSP) to Fresno Chandler Executive Airport (FCH)
Event
- NTSB case
- WPR14FA078
- 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
- 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 172K P
- 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
- N251JM
- Operator
- Timothy Farmer
- Onboard fatalities
- Unknown
- Route
- From Tehachapi Municipal Airport (KTSP), Tehachapi, CATo Fresno Chandler Executive Airport (FCH), Fresno, CA
- Aircraft age
- About 43 years (built 1970)
- 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
- Maneuvering
- 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 control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Physical
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument rated pilot was on a cross-country flight in dark night, hazy, visual flight rules conditions. As the pilot approached his intended destination airport, witnesses observed the pilot attempt to land the airplane three times. During the third attempt to land, the airplane struck a 62-ft-tall tree with the left wingtip; the tree was located about 1,400 ft from the approach end of the runway. The airplane then continued to fly over the runway and entered a left turn. Subsequently, the airplane descended rapidly into the ground. Wreckage and impact signatures were consistent with a near-vertical impact with the ground. Examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures.
Review of the pilot's Federal Aviation Administration medical records revealed that the pilot had not reported any medical conditions. However, according to the pilot's personal medical records, the pilot had elevated cholesterol, gout, high blood pressure, and chronic depression that was in remission; all were adequately controlled and the medications being used were unlikely to impair the pilot's performance.
Although the pilot's corrected visual acuity remained 20/20 bilaterally, he had complained to his optometrist of vision problems with halos around stars. Annual exams documented progression of bilateral cataracts and vitreous opacities in the 4 years before the accident. Cataracts can cause halos around points of light (glare) and degrade night vision. A witness, who was based at the pilot's home airport, reported that the pilot recently had problems taxiing on a familiar lighted runway and taxiway at night. The witness reported that he had to drive his truck onto the taxiway and use the truck's headlights to allow the pilot to find his way off the runway. Based on the pilot's 4-year history of progressive bilateral cataracts, complaints of halos around stars at night, prior difficulty operating the airplane at night on his lighted home airport runway, and his unsuccessful attempts to land on this unfamiliar runway at night, it is likely that cataracts degraded his ability to see clearly at night and resulted in his inability to safely operate the airplane during the accident sequence.
Probable cause
The pilot’s failure to maintain adequate clearance from trees while on approach, which subsequently led to a loss of airplane control. Also causal was the pilot’s continued operation of the airplane at night with a diagnosed medical condition that degraded his night vision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14FA078
- Event ID
- 20131226X23756
- Case number
- WPR14FA078
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-12-27.
- API snapshot SHA-256: 9bd8e6a78188a18e51699a23d74d4c5e89e442dd6e0bec28486a1800ddcddcef; retrieved 2026-09-14T16:09:09.600Z.