FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL07LA130 · Dassault Aviation Mystere Falcon 900

28 Sept 2007 · Teterboro, NJ, United States

Dassault Aviation Mystere Falcon 900 · Accident: on ground/water collision with object while taxiing

From Teterboro Airport (TEB) to San Diego International Airport (SAN)

Report a problem

Event

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

Dassault Aviation Mystere Falcon 900

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
N90TH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), TETERBORO, NJTo San Diego International Airport (SAN), San Diego, CA
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
Taxi · to 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 › Planning/decision, improper

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

NTSB narrative

The captain stated that while taxiing southbound on taxiway "Z," the flight crew felt a sudden "big thud/ jolt." After an inspection of the outside of the airplane, the captain observed damage to the left main wingtip due to a possible collision with a construction steamroller. The steamroller driver stated that after lunch he returned to the construction site and began to operate the steamroller without a wing walker being present. He said that he did not see or hear the airplane as it approached.

Probable cause

The steamroller driver's improper decision to operate the vehicle without a wing walker present.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL07LA130
Event ID
20071011X01543
Case number
ATL07LA130
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, 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: 4c9d692bb22685d67fc4809967a6750daa86a9602d532cd665d20d21044d4fa3; retrieved 2026-09-22T03:23:37.567Z.