FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00LA159 · Aeronca 7BCM

30 Aug 2000 · Santa Fe, NM, United States

Aeronca 7BCM · Accident: total loss of engine power (mechanical failure) on approach

From Moore County Airport (DUX) to Santa Fe Municipal Airport (SAF)

Report a problem

Event

NTSB case
DEN00LA159
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

Aeronca 7BCM

Aircraft type
Aeronca 7
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
N66581
Operator
Bruce N. Barton · private individual
Onboard fatalities
Unknown
Route
From Moore County Airport (DUX), Dumas, TXTo Santa Fe Municipal Airport (SAF)
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
Approach · VFR pattern final
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
Total loss of engine power (mechanical failure)
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

  • Terrain condition › None suitable

Approximate · Estimated position: the centre of Santa Fe, NM, the place the record names. Not the accident site.

NTSB narrative

During approach to land at the completion of a cross-country flight, the pilot attempted to apply power. The engine failed to respond and an emergency landing was conducted on soft, unsuitable terrain. During the landing, the main landing gear separated, the underside of the fuselage was buckled and the wing attach points were deformed near the wing root from damage to the forward attachments. Examination of the engine provided evidence that the needle valve in the carburetor stuck in the closed position for unknown reasons.

Probable cause

Unsuitable terrain for a forced landing. Factors were a complete loss of power due to a stuck needle valve in the carburetor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00LA159
Event ID
20001212X21717
Case number
DEN00LA159
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: 5f045f7b6abcc2820cc0c9bac6ab55c2217b06c769fb4a459183d06af4161dbe; retrieved 2026-09-22T12:30:13.707Z.