FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA012 · Globe GC 1A

9 Oct 2017 · Los Lunas, NM, United States

Globe GC 1A · Accident: loss of control in flight during takeoff

From Mid Valley Airpark (E98) to Las Vegas, NV

Report a problem

Event

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

Globe GC 1A

Aircraft type
Globe GC-1
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
N90365
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mid Valley Airpark (E98), Los Lunas, NMTo Las Vegas, NV
Aircraft age
About 71 years (built 1946)
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
Loss of control in flight
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 airplane arrived to the airport as a refuel stop the day before the accident. During the landing, the airplane ground looped and sustained unknown damage to the airplane. Over the course of that day and the day of the accident, the pilot, who was also a mechanic, completed repairs to the airplane with the assistance from persons at the airport. A portion of the repairs included welding to the right main landing gear link assemblies, and any additional repairs to the airplane were unknown. During takeoff the day following the ground loop, the airplane veered to the left of the runway and struck a berm. The airplane became airborne and then impacted a steel culvert structure adjacent to the runway. The pilot died of his injuries 17 days after the accident. Persons who spoke to the pilot before and after the accident reported the pilot had minimal flying experience in recent years in the accident airplane. The pilot stated during his hospital stay after the accident that there were no mechanical issues during the accident takeoff.

Probable cause

The loss of directional control during takeoff and impact with a steel culvert.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA012
Event ID
20171016X91853
Case number
CEN18LA012
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: 8f4ff5b94f5cda830aabaaa8315582bceb3797a21b15ae2243b555396d4d5ba1; retrieved 2026-09-15T06:21:38.325Z.