FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10FA324 · Cessna T310R

17 Jun 2010 · Ruidoso, NM, United States

Rod Aviation Cessna T310R · Accident: aerodynamic stall/spin on approach

From Granbury Regional Airport (GDJ) to Sierra Blanca Regional Airport (SRR)

Report a problem

Event

NTSB case
CEN10FA324
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
5 · 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 T310R

Aircraft type
Cessna 310
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
N310RH
Operator
Rod Aviation
Onboard fatalities
Unknown
Route
From Granbury Regional Airport (GDJ), Granbury, TXTo Sierra Blanca Regional Airport (SRR), Ruidoso, 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
Defining eventThe 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
Aerodynamic stall/spin
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The airplane was on a visual flight rules cross-country flight and on approach to the airport. A witness, who saw the airplane when it was about 3 miles from the airport, described it as being high for a landing on the runway. He then said the airplane began a “gradual” descent, followed by a “rapid” nose-down descent before it went out of sight. Another witness stated that she saw the airplane suddenly go straight down. One of the passengers stated that, shortly before the accident, the wings were rocking and it felt like the airplane was “tossed around” by the wind. A postimpact fire ensued. An examination of the wreckage indicated that the airplane struck the ground in a 35-degree left bank and about a 52- to 57-degree nose down descent angle; the engines were operating at the time of impact. A postaccident examination of the airplane did not reveal any anomalies indicative of any systems problems prior to the accident. Given the statements of the witnesses, it is likely that the pilot, when he realized the airplane was high on approach, reduced the airplane’s airspeed and raised the nose in order to more rapidly decrease its altitude. The airplane then likely entered an aerodynamic stall, which would have caused the motion felt by the passenger as the airplane rapidly descended nose-down and began rotating before impacting the ground.

While the pilot was experienced in flying multi-engine airplanes, he only had 3.1 hours of flying experience in the accident airplane with a flight instructor and only 5 hours total time in the make and model. Although the investigation was unable to determine what role the pilot’s experience played in the accident, it is likely that his limited experience in the airplane contributed to his lack of airspeed maintenance.

The NTSB has long been concerned about the use of proper restraints in general aviation airplanes. In this accident, an adult and an 11-year-old child were belted in the front passenger seat together. Title 14 Code of Federal Regulations 91.107(a)(3) states that each person “must occupy an approved seat or berth with a safety belt and, if installed, shoulder harness, properly secured about him or her during movement on the surface, takeoff, and landing.” However, the regulation does not specify that all passengers occupy separate seats. On August 11, 2010, the NTSB issued Safety Recommendation A-10-121 asking the FAA to “amend 14 Code of Federal Regulations Part 91 to require separate seats and restraints for every occupant.” The Safety Recommendation is classified “Open—Unacceptable Response,” since the FAA’s proposed clarification of the rule does not discourage or prohibit the unsafe practice of allowing multiple occupants to share a seat and/or restraint system and does not provide clear guidance to general aviation pilots regarding seat belt and seating requirements.

Probable cause

The pilot did not maintain proper airspeed on final approach for landing, which resulted in an aerodynamic stall and impact with terrain. Contributing to the accident was the pilot’s limited experience in the airplane make and model.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10FA324
Event ID
20100617X45846
Case number
CEN10FA324
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 0bf1d62d76cfd0b5a97d8053b5262e9c7250e4833d7d510646e32c2c93fcde42; retrieved 2026-09-13T20:53:06.728Z.