FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA121 · Butler John R SX 300

3 Jan 2012 · Truth or Consequences, NM, United States

Butler John R SX 300 · Accident during takeoff

From Truth or Consequences Municipal Airport (TCS) to Truth or Consequences Municipal Airport (TCS)

Report a problem

Event

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

Butler John R SX 300

Aircraft type
Butler John SX-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
N120J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Truth or Consequences Municipal Airport (TCS), Truth or Consequences, NMTo Truth or Consequences Municipal Airport (TCS), Truth or Consequences, 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
Takeoff
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
Miscellaneous/other
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 structures
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

Prior to takeoff, the pilot forgot to properly latch the canopy. Shortly after rotation, the pilot noticed that the canopy had partially opened, which resulted in a distraction and a loss of airplane control. Subsequently, the airplane contacted the runway, and the landing gear collapsed. The airplane came to rest upright on the side of the runway. Postaccident examination of the airplane revealed that the fuselage was bent and buckled. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot did not maintain airplane control during takeoff due to his distraction with the improperly secured canopy, which he forgot to latch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA121
Event ID
20120104X41711
Case number
CEN12CA121
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: 8fdc75bc0f2ddb5f47a05f28ef629abfe6939475699c754bde9eb856f33ccfc3; retrieved 2026-09-15T17:02:33.749Z.