FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN07FA165 · Cessna T210M

24 Sept 2007 · Moriarty, NM, United States

Cessna T210M · Accident: loss of control in flight on approach

From Albuquerque International Sunport (ABQ) to Moriarty Municipal Airport (0E0)

Report a problem

Event

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

Cessna T210M

Aircraft type
Cessna 210
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
N732XE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Albuquerque International Sunport (ABQ), Albuquerque, NMTo Moriarty Municipal Airport (0E0), Moriarty, NM
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 go-around
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 in flight
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command(cfi) › Aircraft control, not maintained
  • Pilot in command(cfi) › Stall, inadvertent

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

NTSB narrative

The pilot trainee and instructor pilot were conducting the fifth flight in accordance with a training program developed by the operator. Satellite tracking data showed the airplane conducted four touch and go's, and satellite signal was lost on the fifth landing. A pilot-rated witness, who was located in his airplane at a taxiway/intersection, observed the accident airplane appeared to be set up for a short field landing based on the final approach descent angle and full flap position. Approximately 10 to 12 feet above ground level (agl), the airplane appeared to flare and then drop onto the runway. The airplane bounced and became airborne with the wings in a straight and level position. The airplane then drifted to the right of runway centerline, and the witness heard the "engine power come up." The airplane's nose suddenly pitched up and approximately 30 to 40 feet agl, the airplane stalled and impacted the terrain in a nose low attitude. The instructor pilot stated that he had no recall of the accident flight or the previous several days. Examination of the airframe showed the flaps were in the 30-degree extended position, and the elevator trim was approximately 10 degrees nose up. No anomalies were noted that would have precluded normal operations. The pilot's operating handbook supplement for "Balked Landing" procedures required the retraction of flaps to 20 degrees immediately. An elevator trim stall occurs when full power is applied to an airplane configured with excessive nose-up trim. Positive control of the airplane is not maintained resulting in a stall. These types of stalls usually occur during a go-around procedure from a normal landing. During the previous four flights, the instructor pilot noted on a grade sheet that the trainee was "below standards and needs additional training" on areas to include approach to landing stalls, short-field landings, and judgment. In addition, the instructor pilot noted the following comments, "[Trainee] sometimes struggles with aircraft trim, tries to 'muscle' aircraft...Sometimes initiates flare too high, but has enough finesse for a safe landing -- except for short field landings, where he doesn't have the airspeed to sacrifice. For short field approaches, needs to work on a stabilized approach and not flaring high." The operator's program required an initial assessment to be used as a tool to help develop the individual "Master Training Program" which was to serve as the trainee's "roadmap" to gain experience, skills and knowledge necessary to complete the trainee program. An initial assessment was not completed by the operator for this pilot trainee.

Probable cause

the instructor pilot's failure to maintain aircraft control during aborted landing and attempted go-around which resulted in an inadvertent elevator trim stall. Contributing to the accident were the instructor pilot's inadequate supervision during the landing, improper recovery from a bounced landing, and the improper airplane configuration for the attempted go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07FA165
Event ID
20071004X01496
Case number
DEN07FA165
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, 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: 83503108f35917af26547cd49bbc8780c160984cdcedaceeb7aee21527d03ee1; retrieved 2026-09-20T16:15:08.464Z.