OPS08IA010 · Cessna 172
Cessna 172 and Dassault Aviation Falcon 200 · Incident: airport occurrence while taxiing
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- OPS08IA010
- 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
- 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
Aircraft 1 · Cessna 172
- Aircraft type
- Cessna 172
- 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
- N316AS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lincoln Park Airport (N07), Lincoln Park, NJTo Lincoln Park Airport (N07)
- 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 · into takeoff position
- 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
- Airport occurrence
- 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 · Dassault Aviation Falcon 200
- Aircraft type
- Dassault FALCON 200
- 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
- N277QS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (KTEB), Teterboro, NJTo Daniel Oduber Quirós International Airport (MRLB), Daniel Oduber I
- 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
- 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
- Airport occurrence
- 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
On July 9, 2008, at 10:10 am eastern daylight time a runway incursion occurred at the Teterboro Airport (TEB), Teterboro, New Jersey involving N316AS, a Cessna 172 and N277QS, a Dessault Falcon 200 (F2TH). The incident occurred during the day shift with a front line manager and two air traffic control specialists on position. The ground controller had been on position for 40 minutes and was responsible for five aircraft. N316AS had landed on runway 19 and requested a back taxi to runway 19. The ground controller instructed N316AS to taxi to runway 19 via taxiway L and to hold short of runway 19 but did not direct N316AS to hold short of intersecting runway 24. N316AS was already across the hold line for runway 24 but not over the runway edge when the tower controller cleared N277QS for takeoff on runway 24. The takeoff clearance was cancelled. The FAA reported the closest proximity between N316AS and N277QS was 1,200 feet.
Probable cause
Probable Cause
The probable cause of this incident was the TEB ground controller's failure to direct N316AS to hold short of runway 24 when issuing taxi instructions to the aircraft as required FAA Order 7110.65, paragraph 3-7-2 (2a); Taxi and Ground Movement Operations: "When authorizing a vehicle to proceed on the movement area, or an aircraft to taxi to any point other than an assigned takeoff runway, absence of holding instructions authorizes an aircraft/vehicle to cross all taxiways and runways that intersect the taxi route. If it is the intent to hold the aircraft/vehicle short of any given point along the taxi route, issue the route, if necessary, then state the holding instructions".
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS08IA010
- Event ID
- 20080714X01033
- Case number
- OPS08IA010
- 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: f211c69672ce25683e7c347093ee0064db228174192ef92cacdede054961f570; retrieved 2026-09-13T18:13:42.559Z.