FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00LA123 · Beech G18S

6 Jul 2000 · Taos, NM, United States

Beech G18S · Accident: loss of control on ground/water during takeoff

From Saransk International Airport (SKX) to University of Oklahoma Westheimer Airport (OUN)

Report a problem

Event

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

Beech G18S

Aircraft type
Beechcraft 18
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
N1800L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Saransk International Airport (SKX)To University of Oklahoma Westheimer Airport (OUN), Norman, OK
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 · roll/run
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
Loss of control on ground/water
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

  • Dual student › Directional control, not maintained

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

NTSB narrative

The private pilot receiving instruction initiated the takeoff on runway 22. At approximately 40 mph, she raised the tail off the ground in preparation for liftoff. The airplane veered to the left, and the flight instructor took control and aborted the takeoff. The airplane struck a runway light before coming to a stop on the left side of the runway. The flight instructor said that as power was increased for takeoff, the right throttle was advanced slightly ahead of the left throttle, and this, in combination with the gusty crosswind, caused the airplane to veer left off the runway. The wind was from 180 degrees at 17 knots (19 mph), with gusts to 24 knots (28 mph). This would present a 40 degree left quartering headwind. The airplane was not equipped with Geisse safety gear. According to the Crosswind Component Chart contained in the Beech G18S 'Flight Handbook,' the maximum safe crosswind component was not exceeded.

Probable cause

Failure of the pilot receiving instruction to maintain directional control. Factors were a gusty crosswind, inadequate supervision by the flight instructor, and the runway light.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00LA123
Event ID
20001212X21433
Case number
DEN00LA123
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: c093379ba5b8b8728cb4475931e4d5c8470483ed6a5fb500d70ff35bc82e0a06; retrieved 2026-09-22T12:43:47.490Z.