AirNet Systems Bombardier, Inc. 35A accident
Bombardier, Inc. 35A · Accident: ground collision while taxiing
From Philadelphia International Airport (PHL) to Charlotte Douglas International Airport (CLT)
Event
- NTSB case
- NYC08CA088
- 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
- Charter & commuter
- 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
Bombardier, Inc. 35A
- Aircraft type
- Bombardier 35
- 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
- N55F
- Operator
- Airnet Systems
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo Charlotte Douglas International Airport (CLT), Charlotte, NC
- 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 135: Air Taxi & Commuter
- 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
- 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
- Ground collision
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A Bombardier (LearJet) 35A had just landed, and was taxiing on taxiway A during night conditions. A tug was traveling south on an access road, and approaching the taxiway A stop sign. The tug did not slow for the stop sign, traveled past it, and struck the nose of the airplane. The stop sign had flashing red lights that were operating at the time of the collision, and the driver of the tug did not report any preimpact mechanical malfunctions with the vehicle. The recorded weather at the airport, about the time of the accident, included scattered clouds at 3,800 feet, and 8 miles visibility in light rain.
Probable cause
The tug driver's failure to stop for a taxiway stop sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA088
- Event ID
- 20080305X00268
- Case number
- NYC08CA088
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, 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: 9148d60add0b776503c08eea6d3335d8b6f33b4c95b6c987be5b5efe3560f2e6; retrieved 2026-09-15T09:24:25.533Z.
- The NTSB's operator name is blank for N55F; the operator shown is the name the NTSB's other records give its FAA operator code, BSYA.