FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA037 · Bates STARDUSTER SA-300

27 Oct 2012 · Reklaw, TX, United States

Bates STARDUSTER SA-300 · Accident: nose over/nose down during landing

From Mesquite Metro Airport (KHQZ) to Flying M Ranch Airport (7TA7)

Report a problem

Event

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

Bates STARDUSTER SA-300

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
N2369
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mesquite Metro Airport (KHQZ), Mesquite, TXTo Flying M Ranch Airport (7TA7), Reklaw, TX
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
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
Nose over/nose down
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 › Task performance

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

NTSB narrative

The pilot reported that he was landing on a private grass airstrip and that the grass was wet from the previous night’s rain. He stated that the airstrip was not flat and had sections that rolled up and down. He added that the airplane touched down harder than usual, which caused the landing gear to spread outward on the wet grass. The engine’s propeller was then low enough to contact the rising terrain, and the airplane nosed over. A witness reported that the airplane bounced on the runway about three times before the airplane nosed over. The airplane came to rest in the inverted position, resulting in substantial damage to the vertical stabilizer, top wings, and the engine firewall.

Probable cause

The pilot’s improper recovery from a bounced landing, which resulted in a noseover.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA037
Event ID
20121031X14410
Case number
CEN13CA037
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: a8f89250522b21c9cd783e4a9ff8ffb140682c8b8e193f76bb37905907ec753b; retrieved 2026-09-15T20:18:38.352Z.