LAX94LA094 · Cessna 140
Cessna 140 · Accident: loss of engine power en route
From McClellan-Palomar Airport (CRQ) to Chiriaco Summit Airport (L77)
Event
- NTSB case
- LAX94LA094
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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 140
- Aircraft type
- Cessna 140
- 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
- N140KT
- Operator
- Daniel J. Moriarty · private individual
- Onboard fatalities
- Unknown
- Route
- From McClellan-Palomar Airport (CRQ), Carlsbad, CATo Chiriaco Summit Airport (L77), CHIRIACO SUMMIT, 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 · climb to cruise
- First occurrenceThe 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 engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT THE AIRCRAFT WAS IN A CRUISE CLIMB CONFIGURATION WHEN THE ENGINE BEGAN TO LOSE POWER. THE PILOT DESCRIBED THE POWER LOSS AS A SLOW DECREASE IN RPM'S FOLLOWED BY A 'PULSING AT LOW RPM.' THE PILOT BEGAN A DESCENT AND ATTEMPTED TO REMEDY THE POWER LOSS BY CHANGING THE MIXTURE SETTING AND APPLYING CARBURETOR HEAT. POWER COULD NOT BE RESTORED AND THE PILOT LANDED IN A PASTURE. DURING THE LANDING GROUND ROLL, THE AIRCRAFT COLLIDED WITH THE LIP OF A RAVINE. AN FAA AIRWORTHINESS INSPECTOR EXAMINED THE AIRCRAFT. THE INSPECTOR STATED THAT FUEL WAS EVIDENT IN THE TANKS, LINES, AND GASCOLATOR BOWL. THE PROPELLER AND IMPACT DAMAGED INTAKE SPIDER MANIFOLD WERE REPLACED. THE ENGINE WAS THEN STARTED AND RAN FOR SEVERAL MINUTES, UP TO 2,000 RPM, UTILIZING THE AIRFRAME FUEL AND IGNITION SYSTEM COMPONENTS. THE CARBURETOR WAS DISASSEMBLED WITH NO INTERNAL ABNORMALITIES NOTED.
Probable cause
a loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA094
- Event ID
- 20001206X00640
- Case number
- LAX94LA094
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 3e9cdc65527a8d21c97309c138eec2ec759add5fe2a29ce0338766ba548d9232; retrieved 2026-09-21T22:43:31.470Z.