FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15TA019 · BAE Systems HAWK MK 67

18 Oct 2014 · Oklahoma City, OK, United States

Air USA BAE Systems HAWK MK 67 · Accident: runway excursion during takeoff

From Tinker Air Force Base (KTIK) to Cherry Point, NC

Report a problem

Event

NTSB case
CEN15TA019
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
Government
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

BAE Systems HAWK MK 67

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
N509XX
Operator
Air USA
Onboard fatalities
Unknown
Route
From Tinker Air Force Base (KTIK), Oklahoma City, OKTo Cherry Point, NC
Aircraft age
About 21 years (built 1993)
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
Public Aircraft
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
Runway excursion
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was on a cross-country flight in a single-engine jet trainer and had stopped en route for refueling. The pilot reported that, during the takeoff roll, as the airspeed reached about 90 knots, the airplane made a hard left turn. He applied the right rudder and brake to stop the left turn; however, the airplane continued left off the runway surface and then came to rest upright.

Examinations of the tires, wheel brakes, and rudder did not reveal any abnormalities. The nosewheel steering control unit was bench tested. During the test, the unit's power supply module failed; however, it was determined that a supply failure would cause a castering nosewheel rather than an uncommanded steering input. The reason for the uncommanded turn could not be determined.

Probable cause

The loss of directional control during the takeoff roll for reasons that could not be determined during postaccident examinations and testing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15TA019
Event ID
20141020X70229
Case number
CEN15TA019
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, coordinates. 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: a9596b3595be78481ec9b2fd3600ec9984c665a9fe8c890e8ff201b19769546d; retrieved 2026-09-16T01:52:11.189Z.