FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

OPS08IA004 · Gulfstream American G5

27 Dec 2007 · Teterboro, NJ, United States

Gulfstream American G5 and East Coast Jets Raytheon Corporate Jets H25B · Incident: near collision between aircraft during takeoff

Report a problem

Event

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

Aircraft 1 · Gulfstream American G5

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
N90AM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo PBI · West Palm Beach, FL
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
Takeoff
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
Near collision between aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Raytheon Corporate Jets H25B

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
N818MV
Onboard fatalities
Unknown
Route
From Lehigh Valley International Airport (ABE), Allentown, PATo Teterboro Airport (TEB), Teterboro, NJ
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 · 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
Near collision between aircraft
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

  • Atc personnel(lcl/gnd/clnc) › Air/ground communications, improper
  • Control tower › Improper

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

NTSB narrative

On December 27, 2007, 0802 Eastern Standard time, a runway incursion occurred at Teterboro Airport (TEB), Teterboro, New Jersey involving East Coast Jets (ECJ) flight 81, registration number N818MV, a Hawker 25, and N90AM, a G5. There was training in progress on ground control and there was a certified professional controller on local control. Tower staffing included a tower supervisor, a local controller, a ground controller and ground control developmental and a fight data/clearance delivery controller. ECJ 81 had landed on runway 6 and was advised by the local controller after landing to "turn left at taxiway bravo if able, cross [runway] one contact ground". ECJ81 exited the runway at taxiway B and contacted ground control for taxi to the Meridian FBO located on the north side of the airport. The developmental ground controller requested approval from the tower local controller to taxi ECJ81 across runway 1 at taxiway B. The local controller approved the request. About this time, N90AM called local control for takeoff and was directed to taxi into position and hold on the approach end of runway 1. The local controller, who was responsible for 2 aircraft and had 2 previous operational errors with some similarities, cleared N90AM for takeoff as ECJ81 was crossing the runway. The developmental ground controller reminded the local controller of the crossing and advised that it was not complete. The local controller, anticipating that appropriate separation would exist prior to N90AM beginning takeoff roll, instructed ground controller to expedite the crossing of ECJ81 and did not cancel the takeoff clearance. According to the Federal Aviation Administration, the closest proximity was 4,000 feet. The incident occurred during day visual meteorological conditions.

Probable cause

The probable cause of this incident was the TEB tower local controller's failure to ensure that the runway was free of all known ground vehicles, equipment, and personnel before permitting a departing aircraft to start takeoff roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS08IA004
Event ID
20080128X00107
Case number
OPS08IA004
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, 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: 43b93e5e07defb6476651e6ed75cb4842d7bd402b790b8f5cbbcdc557c4981fd; retrieved 2026-09-18T14:39:11.467Z.