FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI92DCG02 · A. H. Gettings GLASSAIR SH2 GLASSAIR S

30 May 1992 · Marshall, MO, United States

A. H. Gettings GLASSAIR SH2 GLASSAIR S · Accident: airframe, component or system failure during takeoff

From Marshall Memorial Municipal Airport (MHL) to East Kansas City Airport (3GV)

Report a problem

Event

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

A. H. Gettings GLASSAIR SH2 GLASSAIR S

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
N18KG
Operator
Albert H. Gettings · private individual
Onboard fatalities
Unknown
Route
From Marshall Memorial Municipal Airport (MHL)To East Kansas City Airport (3GV), Grain Valley, MO
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 · rejected takeoff
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
Airframe, component or system failure
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 › Procedures/directives, inadequate

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

NTSB narrative

THE PILOT OF THE ACCIDENT AIRPLANE STATED HE HEARD A 'POP' DURING A TAKEOFF GROUND RUN AND ABORTED THE TAKEOFF. HE CHECKED THE FLIGHT CONTROLS AND ELECTED TO ATTEMPT ANOTHER TAKEOFF. AS THE AIRPLANE ACCELERATED AFTER POWER APPLICATION THE PILOT DISCOVERED HE COULD NOT MAINTAIN DIRECTIONAL CONTROL EVEN WITH FULL DEFLECTION OF THE FLIGHT CONTROLS AND HEAVY RIGHT BRAKE APPLICATION. HE ELECTED TO ABORT THE TAKEOFF AGAIN. DURING THE SECOND ABORT THE RIGHT WING STRUCK THE GROUND AND THE RIGHT FUEL TANK RUPTURED. THE AIRPLANE WAS DESTROYED IN AN ONGROUND FIRE. A POST ACCIDENT INSPECTION REVEALED A BROKEN RIGHT RUDDER PEDAL ATTACHMENT TUBE.

Probable cause

THE PILOT'S INADEQUATE PRE-TAKEOFF FLIGHT CONTROL CHECK.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI92DCG02
Event ID
20001211X14611
Case number
CHI92DCG02
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 2dad74fedf10617bb8076974c6a818292749c48d579ec2f6194f155720ee3c59; retrieved 2026-09-23T03:06:41.310Z.