WPR12FA139 · Beech B36 TC
Jim Lafferty Aircraft Sales Beech B36 TC · Accident: controlled flight into terrain/object (CFIT) en route
From St Johns Industrial Air Park (SJN) to Hollister Municipal Airport (CVH)
Event
- NTSB case
- WPR12FA139
- 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
- 1 · 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
- Unknown
Beech B36 TC
- Aircraft type
- Beechcraft 36
- 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
- N364AB
- Operator
- Jim Lafferty Aircraft Sales
- Onboard fatalities
- Unknown
- Route
- From St Johns Industrial Air Park (SJN), St Johns, AZTo Hollister Municipal Airport (CVH), Hollister, CA
- Aircraft age
- Not recorded
- 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 · descent
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was delivering the single engine airplane from England to the west coast of the United States. According to his resume, he had piloted 196 Atlantic crossings in general aviation airplanes. The trip began about 1 week before the accident. The flights from England to Maine, with a pilot-rated passenger on board, consisted of 6 legs, with a total flight time of about 27 hours over a period of about 96 hours.
The passenger and pilot separated in Bangor, Maine, and the pilot continued to Kentucky that same day, with an additional 2 legs and 6 hours flight time. He spent a total of 13 hours on the ground in Kentucky before departing early in the morning on the day of the accident. The first leg was 5 hours followed by a fuel stop. The next leg was 3 hours 20 minutes, and another fuel stop was made. The pilot then departed on the accident leg to his destination in California.
The pilot flew the over 4-hour accident leg under visual flight rules using air traffic control flight following services. He flew directly between waypoints instead of on established airways. The airplane was equipped with a panel-mounted GPS unit with altitude information capability, and the pilot's iPad was equipped with current flight planning and guidance software, and electronic navigation charts. The pilot had access to sufficient information in flight to remain clear of terrain, but the investigation was unable to determine whether the pilot accessed that information during any part of that flight leg.
When the airplane was about 65 miles from its destination, the pilot began a steady descent from his cruise altitude of 12,500 feet, which he had flown without supplemental oxygen. The destination elevation was 230 feet.
Due to coverage limitations, radar contact with the airplane was lost when it was descending through 5,100 feet. At this point, the airplane was 46 miles from its destination, and the controller cancelled the flight-following services. There were no further communications from the pilot; up to this point, he had acknowledged all transmissions from ATC. Twelve miles after flight-following services were cancelled, the airplane impacted a hillside at an elevation of about 1,960 feet. Ground scar and wreckage information indicated that the airplane impacted in a wings-level attitude on a near-horizontal flight path. The airplane was highly fragmented and damaged by postimpact fire. Evidence was consistent with the landing gear and flaps retracted. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.
Darkness prevailed at the time of the accident, and AIRMETs for mountain obscuration were current for the time and location of the accident. Satellite and weather radar data suggested the presence of instrument meteorological conditions along parts of the airplane's route, but the investigation was unable to determine whether the pilot encountered or entered instrument meteorological conditions during the descent.
Extrapolation of radar-derived speed and descent rate data indicated that the airplane descended steadily on track from cruise to the impact point. The pilot's autopsy indicated that the cause of death was multiple blunt trauma injuries, with no adverse pre-existing conditions. The effects of possible fatigue or hypoxia on the pilot's performance could not be determined.
Probable cause
The pilot’s lack of situational awareness regarding the surrounding terrain while descending during dark night conditions, which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA139
- Event ID
- 20120317X91318
- Case number
- WPR12FA139
- 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 2012-03-15.
- API snapshot SHA-256: 055a4f8cbe67da0e40390d4dfc08d5d00b3e511b60026899dcbaedfe77e022d7; retrieved 2026-09-13T22:14:59.004Z.