FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA412 · Quicksilver MXII SPORT

25 Jun 2009 · Longmont, CO, United States

Quicksilver MXII SPORT · Accident: loss of engine power (partial) on approach

From Longmont, CO to Longmont, CO

Report a problem

Event

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

Quicksilver MXII SPORT

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
N2910P
Onboard fatalities
Unknown
Route
From Longmont, COTo Longmont, CO
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 (partial)
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 power plant

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

NTSB narrative

The student pilot reportedly purchased the airplane several months prior to the accident, and was on a local flight when the accident flight occurred. The pilot stated that the airplane got low during an approach to the runway, so he added engine power, but the engine did not respond. The airplane then impacted a guardrail short of the runway. The Federal Aviation Administration (FAA) Inspector, who responded to the scene, stated that the pilot had reported putting 5 gallons of fuel in the airplane prior to flight, that the pilot had been airborne for about an hour, and the engine used about 4 gallons per hour. In a telephone interview with the NTSB Investigator in Charge (IIC), the pilot stated the engine did not produce power during the approach, and he thought that the airplane might have encountered carburetor icing. The pilot failed to submit a NTSB form 6120.1, Pilot/Operator Accident/Incident Report, as requested.

Probable cause

The loss of engine power for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA412
Event ID
20090707X93229
Case number
CEN09CA412
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: 2413b6d1303170887d2ae90306d72c377deaab9321bc17f0de9e774b2d96f96e; retrieved 2026-09-15T11:44:09.188Z.