DEN82DA169 · Quicksilver MXII
Quicksilver MXII · Accident: in flight collision with object during takeoff
From Rocky Mountain Metropolitan Airport (BJC) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- DEN82DA169
- 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
Quicksilver MXII
- Aircraft type
- Quicksilver MXII
- 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
- N3149Z
- Operator
- Jamee J. Andersen · private individual
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, 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
- Takeoff
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Pilot in command › Aircraft weight and balance, exceeded
- Pilot in command › Airspeed, not maintained
- Pilot in command › Maneuver, delayed
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
REPORTEDLY, THE PILOT MADE AN INTERSECTION TAKEOFF FROM ABOUT MIDFIELD ON RUNWAY 02. HE STATED THAT HE TOOK OFF AT ROTATION SPEED PLUS 2 KTS. THE PASSENGER REPORTED THAT THEY REACHED ABOUT 40 FT AGL, THEN LOST LIFT AND BEGUN TO SETTLE. AS THE TWO-PLACE ULTRALIGHT AIRCRAFT SETTLED, IT WAS HEADED TOWARD AN AIRPORT NOISE ABATEMENT SIGN. THE PILOT ATTEMPTED TO TURN THE AIRCRAFT TO AVOID THE SIGN, BUT THE PLANE STRUCK IT HEAD-ON. AN INVESTIGATION REVEALED THAT THE PLANE WAS 10 LBS OVER ITS MAXIMUM GROSS WEIGHT AND THE DENSITY ALTITUDE WAS 8056 FT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN82DA169
- Event ID
- 20020917X03188
- Case number
- DEN82DA169
- 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: b8f2a6ec2b51fdd85a82360e732ea0c2e062f66a7f8981d6ee843d6de2bc65d3; retrieved 2026-09-21T18:08:43.852Z.