Quicksilver MXII SPORT accident near Longmont, Colorado, June 25, 2009
On June 25, 2009 at about 2:10 pm local time, a Quicksilver MXII SPORT, registered N2910P, was substantially damaged in an accident during approach (VFR pattern final) near Longmont, Colorado. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 25, 2009 · about 2:10 pm local time
- Place
- Longmont, Colorado · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Quicksilver MXII SPORT
- Registration
- N2910P · registry record · serial 000772
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during approach (VFR pattern final) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Not specified
Dual student
- Certificate: student
- Flight time: 99 hours in all; 99 in this make and model
- Medical certificate: None
- Seat: unk
- Injury: minor injuries
The aircraft
- Last inspection: inspection type not recorded
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 582 (piston); 0 hours total
The flight
- Departed from: Longmont CO
- Destination: Longmont CO
- Flight plan: not recorded
Weather at the time
- Light: daylight
- Wind: at 4 knots
- Visibility: 40 statute miles
- Sky: a few clouds at 70 ft
- Temperature: 72°F (22°C), dew point 48°F (9°C)
- Altimeter: 30.19 inHg
- Observation at 2:55 pm, 15 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N2910P the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.