FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11FA268 · Trusty THORP T-18

19 Jun 2011 · Tehachapi, CA, United States

Trusty THORP T-18 · Accident: controlled flight into terrain/object (CFIT) en route

From Santa Ynez Airport (IZA) to Tehachapi Municipal Airport (TSP)

Report a problem

Event

NTSB case
WPR11FA268
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
Visual Meteorological Cond

Trusty THORP T-18

Aircraft type
Trusty THORP T-18
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
N851LT
Operator
Trlica Lee G
Onboard fatalities
Unknown
Route
From Santa Ynez Airport (IZA), Santa Ynez, CATo Tehachapi Municipal Airport (TSP), Tehachapi, 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 · cruise
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Physical
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was making an approximate 40-minute flight to his home airport during daylight visual meteorological conditions. After he did not check in at his expected arrival time, his family reported him overdue. The wreckage was subsequently located by a local resident after he observed debris on a road, looked over the edge of a mountain, and saw the accident site.

Radar data showed the airplane traversing a mountain range in a straight-and-level flightpath, entering an adjoining valley, and then entering a descent of between 700 and 900 ft per minute. The last radar return was about 15 miles from the accident site, which was located about 200 ft below the ridgeline on the west-facing side of the 4,400-ft-tall mountain. The airplane impacted the rising terrain in a wings-level attitude. Postaccident examination of the airframe and engine revealed no mechanical anomalies that would have precluded normal operation.

About 6 months before the accident, the pilot and his wife reported a significant change in the pilot's behavior to the pilot's endocrinologist, who prescribed further medical evaluation and consultation; however, no records of any further evaluation or consultation were found. Postmortem toxicology tests on the pilot identified donepezil, which is used to slow the progression of dementia in Alzheimer's disease. The medication does not carry a specific warning, but it has been associated with fainting, dizziness, and other neurological symptoms in some patients. Although it could not be determined whether the pilot was impaired by the effects of donepezil at the time of the accident and the exact extent of the pilot's cognitive decline could not be determined, it is likely that he was cognitively impaired and, thus, at an increased risk for an accident.

The pilot also had other chronic medical problems, including diabetes, hypertension, and high cholesterol. Further, the pilot's autopsy revealed that he had moderate-to-severe coronary artery disease and biventricular hypertrophy, which placed him at risk for impairment or incapacitation from a cardiac event such as acute ischemia or arrhythmia that would not be evident during an autopsy. Thus, he may have been impaired or incapacitated at the time of the accident as a result of his extensive heart disease.

Postmortem toxicology testing on the pilot also detected metoprolol (a beta blocker used to treat high blood pressure and control heart rate); however, it is not likely that it impaired the pilot. Further, the testing detected therapeutic levels of the antihistamine doxylamine, which due to its significant sedating effects is also marketed as an over-the-counter sleep aid and carries the warning that, at therapeutic levels, it "may impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery)." It is likely that the pilot was impaired by doxylamine at the time of the accident.

Probable cause

The pilot’s failure to maintain clearance from mountainous terrain during cruise flight, which resulted from his impairment or incapacitation due to multiple medical conditions and sedating medication.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11FA268
Event ID
20110620X22349
Case number
WPR11FA268
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-06-20.
  • API snapshot SHA-256: f8c95b17af0a8db5f676094465ec7c02d93d5098b70db881d20fe5fda2dd18a4; retrieved 2026-09-13T21:28:24.491Z.