FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

B & M Enterprises Cessna T210M accident

6 Aug 1999 · Clovis, NM, United States

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

From Dallas Love Field (DAL) to Clovis Municipal Airport (CVN)

Report a problem

Event

NTSB case
DEN99FA137
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
Charter & commuter
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
N6687B
Onboard fatalities
Unknown
Route
From Dallas Love Field (DAL), DALLAS LOVE, TXTo Clovis Municipal Airport (CVN)
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 135: Air Taxi & Commuter
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 pattern final
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 › Airspeed, not maintained

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

NTSB narrative

The non-scheduled domestic cargo flight was en route from Dallas, Texas, to Clovis, New Mexico, with no cargo aboard, and was scheduled to pick up checks in Clovis. The pilot was overheard announcing his position over the airport's UNICOM frequency when the airplane was 15, 10 and 5 miles out for landing at Clovis, but was never observed to have landed. A witness 1 mile east of the airport, overheard the airplane's engine accelerate, and observed the airplane to be 'lower and slower' than most aircraft at that altitude inbound for landing. The airplane was level for several seconds, then 'turned into a nose dive and crashed.' A search for the airplane was initiated, and it was located .57 nm from the approach end of runway 22 approximately 1 hour later. The weather at the time of the accident was clear skies with winds from 200 degrees at 15 knots. The density altitude was calculated to be 6,648 feet above msl.

Probable cause

The pilot's failure to maintain sufficient airspeed during final approach to landing, resulting in an inadvertent stall. A factor was the high density altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN99FA137
Event ID
20001212X19477
Case number
DEN99FA137
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: a5d2304e44292e3c2903ecdab1bbb00034ab33ebebeffa2c23196b4522ac12cf; retrieved 2026-09-18T13:17:09.163Z.
  • The NTSB's operator name is blank for N6687B; the operator shown is the name the NTSB records it doing business as.