FTW98FA283 · Montgomery QUICKIE TRI-Q/200 QUICKIE TR
Montgomery QUICKIE TRI-Q/200 QUICKIE TR · Accident: loss of control on ground/water while taxiing
From FWS to an unrecorded destination
Event
- NTSB case
- FTW98FA283
- 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
- 1 · 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
Montgomery QUICKIE TRI-Q/200 QUICKIE TR
- Aircraft type
- Montgomery QUICKIE TRI-Q 200
- 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
- N699WB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From FWSTo 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
- Taxi
- 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
- Loss of control on ground/water
- 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 control, not obtained/maintained
- Pilot in command › Lift-off, inadvertent
- Pilot in command › Taxispeed, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a high speed taxi at the non towered airport, the homebuilt Quickie airplane inadvertently became airborne. The airplane entered vertical oscillations combined with yawing & banking, rolled inverted and descended vertically to ground impact. The 556 hr pilot/owner/builder had 6 hrs of dual in the past 12 years. He had 50+ hrs of taxi runs in the Quickie; however, no flight time and 'no intention of flying the airplane.' The pilot's manual recommends 10 hrs of flying time within the 3 months prior to flight testing the airplane, and during taxi tests to 'always be prepared for a liftoff and first flight if it should accidentally occur.' Lift-off speed is given as 70 mph. Another pilot reported that a bump on the runway caused the nose wheel to lift-off once when he was taxiing the airplane. This pilot, who also had the airplane inadvertently lift-off in ground effect at 85 mph, experienced 'no control problems.' Flight control continuity was confirmed. No pre-impact discrepancies were found.
Probable cause
The pilot's failure to maintain aircraft control when an excessive taxispeed resulted in an inadvertent lift-off of the airplane. A factor was the pilot's lack of total experience in the make and model of aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98FA283
- Event ID
- 20001211X10294
- Case number
- FTW98FA283
- 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: 954112b793bfc7685a26edd9b7191d8e1823a5caa689b79b2c8906c5e05b9c0c; retrieved 2026-09-20T22:31:44.425Z.