FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN99LA143 · Moore Q-200

11 Aug 1999 · Cortez, CO, United States

Moore Q-200 · Accident: hard landing

From Tucumcari Municipal Airport (TCC) to Cortez Municipal Airport (CEZ)

Report a problem

Event

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

Moore Q-200

Aircraft type
Moore 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
N321TM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tucumcari Municipal Airport (TCC), Tucumcari, NMTo Cortez Municipal Airport (CEZ)
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
Landing · flare/touchdown
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
Hard landing
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 › Recovery from bounced landing, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

As he approached the airport, the pilot was advised that the wind was from the south approximately 5 to 10 mph, and that the runway was wet as the result of a recent rain shower. The pilot entered the traffic pattern and carried power throughout the approach to runway 21. When the airplane was flared and power reduced for landing, the nose dropped onto the runway. The airplane bounced and skewed 30 degrees to the left. The pilot added full power but the airplane did not appear to gain altitude or airspeed. Because of tall vegetation ahead, the pilot decided to land. He reduced power and landed on the grass, then straightened the airplane to parallel the runway. The airplane rolled into a muddy area and nosed down.

Probable cause

The pilot's improper recovery from a bounced landing and his failure to maintain directional control. Related factors were the soft wet terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN99LA143
Event ID
20001212X19488
Case number
DEN99LA143
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: 62cc6968c25c832dff94af310efefe1d281e2f5dc814282a14b56c1efd4272cd; retrieved 2026-09-22T14:19:15.049Z.