USAirways Airbus A320 incident
Airbus A320 · Incident: runway incursion (vehicle, aircraft or person) during takeoff
Event
- NTSB case
- OPS09IA008
- 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
- Incident
- 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
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Airbus A320
- Aircraft type
- Airbus A320
- Category
- Airplane · from aircraft type
- 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
- N662AW
- Operator
- USAirways
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 121: Air Carrier
- 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 incursion (vehicle, aircraft or person)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane rotated approximately 500 feet from the intersection of runway 15R and taxiway M as the vehicle cleared the runway edge southbound on taxiway M. Taxiway M was under construction to connect the northern and southern portions for a full-length parallel taxiway. The operator of the construction vehicle was just coming on shift at the construction site at taxiway M. The Airport Authority had designated the south haul route as active at the time of the incident. The operator of the construction vehicle departed the construction trailer and drove to the construction site via the north haul route. He recalled turning on the construction vehicle’s rotating lights and the radio. He made no radio contact with the tower air traffic controllers during the drive, and despite not seeing any stop signs in place indicating a closed runway or looking both ways at the intersection, crossed the active runway without clearance. The operator of the vehicle stated in his interview he was “on autopilot during the drive to the construction site” and “was preoccupied” with thoughts of what needed to be done at the construction site.
Probable cause
The vehicle operator's failure to follow the designated haul route to the construction site and his failure to adhere to airport driving procedures, which led to missed visual cues and lack of required communication prior to crossing the active runway. Contributing to the incident was the vehicle operator's distraction.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS09IA008
- Event ID
- 20090619X84742
- Case number
- OPS09IA008
- 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, damage. 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: 4e53d0978e8b5c5985e7314329b43a1f454d420be65356576a9697f03ecb2a3e; retrieved 2026-09-15T11:30:12.368Z.