FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

USAir Express Beech 1900D accident

15 Oct 1997 · Pittsburgh, PA, United States

Beech 1900D · Accident: on ground/water collision with object while taxiing

From Youngstown Warren Regional Airport (YNG) to Pittsburgh International Airport (PIT)

Report a problem

Event

NTSB case
NYC98LA013
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
Airline
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 1900D

Aircraft type
Beechcraft 1900
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
N162ZV
Onboard fatalities
Unknown
Route
From Youngstown Warren Regional Airport (YNG), Youngstown, OHTo Pittsburgh International Airport (PIT)
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
Taxi · from runway
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
On ground/water collision with object
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

  • Driver of vehicle › Instructions, written/verbal, not followed

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

NTSB narrative

The First Officer was taxiing the airplane to the gate after landing. The airplane was traveling south on a taxiway when the Captain noticed a baggage tug approaching on an access road perpendicular to the taxiway from the left, traveling west. The Captain applied the brakes to stop the airplane; however, the tug continued and collided with the airplane's left wing. The tug driver said he may have lost consciousness after striking a bump in the access road. The police reported the bump was at the point where the access road intersected the taxiway, and the intersection was controlled by a stop sign on the access road. The Police Officer issued a citation to the tug driver for violation of a county ordinance, which stated, 'Aircraft always have the right-of-way in the AOA. Vehicles needing to traverse an AOA ramp shall...obey all posted signage.'

Probable cause

the tug driver's failure to obey a stop sign and his failure to yield right-of-way to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC98LA013
Event ID
20001208X09107
Case number
NYC98LA013
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: 357e6d1a592d52e9b53720eae0e5028130c1a3cf77f6e6bacda0f2e6c8d74b17; retrieved 2026-09-18T17:20:44.870Z.
  • The NTSB's operator name is blank for N162ZV; the operator shown is the name the NTSB records it doing business as.