FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA08LA034 · Costruzioni Aeronautiche P2002 Sierra

3 Jan 2008 · Stevensville, MD, United States

Costruzioni Aeronautiche P2002 Sierra · Accident: loss of engine power (total) on approach

From Bay Bridge Airport (W29) to an unrecorded destination

Report a problem

Event

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

Costruzioni Aeronautiche P2002 Sierra

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
N26WR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bay Bridge Airport (W29), Stevensville, MDTo not recorded
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
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 engine power (total)
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 handling/service
  • Personnel issues › Task performance

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

NTSB narrative

While on short final approach the pilot reduced engine power to idle and the engine lost power. A forced landing was made in a field short of the runway and the airplane incurred substantial damage. Examination of the engine by a Federal Aviation Administration inspector, and a representative of the engine manufacturer revealed that the carburetor mixture and throttle stop were found to be out of adjustment. The Rotax maintenance manual requires checking of these adjustments during each 100-hour inspection.

Probable cause

A loss of engine power due to the failure of company maintenance personnel to comply with engine manufacturers requirements for carburetor adjustment during the 100-hour inspection.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA08LA034
Event ID
20080115X00046
Case number
MIA08LA034
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: investigation status, coordinates. 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: 1d4e5e4941d061c05bd52f9c85eceae4a82c45a17794e6099f7698d266ecde32; retrieved 2026-09-15T09:20:14.769Z.