Teterboro, NJ, USA
N316AS
Cessna 172
N277QS
Dassault Aviation Falcon 200
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.
On July 9, 2008, at 10:10 am eastern daylight time, a runway incursion occurred at Teterboro Airport (TEB), Teterboro, New Jersey involving N316AS, a Cessna 172, and N277QS, a Dassault Falcon 2000 (F2TH). The incident occurred during the day shift with a front line manager, three air traffic control specialists and one developmental controller on position in the control tower. 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 for a departure to the northwest. 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 N277QS had been cleared for takeoff on runway 24. The local controller, observing N316AS' encroachment onto runway 24, canceled N277QS' takeoff clearance. Closest proximity between N316AS and N277QS was 1,200 feet. The incident occurred during day visual meteorological conditions. HISTORY OF FLIGHT N316AS had departed Lincoln Park Airport, Lincoln Park, New Jersey (N07) located 13 miles northwest of the Teterboro Airport, Teterboro, New Jersey (TEB) on a visual flight rules (VFR), Part 91, pleasure flight. N316AS landed at TEB on runway 19 at approximately 10:08 am. After clearing the runway at taxiway Q, the ground controller queried N316AS of his destination on the airport. N316AS advised the ground controller that he wanted to depart TEB to the northwest. Ground control instructed N316AS to taxi to and hold short of runway 19 via taxiway L. Taxiway L crosses runway 24 between taxiway Q and the approach end of runway 24. N316AS was not directed to hold short of runway 24. The tower local controller instructed N277QS to taxi into position and hold on runway 24 in order to allow adequate separation to develop between the previous departure. N277QS was departing TEB on an IFR part 135 flight to the Daniel Oduber International Airport, Liberia, Costa Rica (MRLB). At approximately 10:10 am, the local controller cleared N227QS for takeoff. As N227QS began takeoff roll, the local controller observed N316AS approaching runway 24 and did not appear to be slowing down. The local controller canceled the take off clearance for N277QS as the front line manager directed the ground controller to stop N316AS. The local controller also issued a go-around to an arriving aircraft inbound for runway 24. N316AS crossed the hold short line of runway 24 but did not proceed onto the runway surface area before bringing the aircraft to a stop. N277QS reduced his ground speed to taxi speed, completed a 180-degree turn on the runway and returned to the approach end of runway 24 as directed by the local controller. N277QS departed TEB shortly thereafter. N316AS departed TEB off runway 24 shortly after N277QS. PERSONNEL INFORMATION N277QS had a flight crew of three with a pilot, a co-pilot or first officer and one flight attendant and six passengers on board for a total of 9 people. N316AS had a single pilot on board with no passengers or co-pilot. The TEB tower ground controller entered duty with the FAA in July 2007 and had been certified on the ground control position on June 26, 2008. METEOROLOGICAL INFORMATION The TEB weather observation at 9:51 am was: wind 210 at 8 knots, visibility 9 statute miles, sky clear, temperature 27, dew point 21, altimeter 29.81 AIRPORT INFORMATION Teterboro Airport serves general aviation aircraft. The annual air activity averages 200,000 operations per year. The airport is configured with two intersecting runways, runway 1/19 which was 7000 feet by 150 feet and 6/24 which was 6013 feet by 150 feet. The two runways intersect 1800 feet from the approach end of runway 24 and approximately 1000 feet from the approach end of runway 19. WRECKAGE AND IMPACT INFORMATION There was no damage or injuries reported for either aircraft. ADDITIONAL INFORMATION Air Traffic Control Information TEB Air Traffic Control Tower (ATCT) was an ATC-7 level facility responsible for aircraft operations on the airport surface and in the Class D airspace in the immediate vicinity of the airport. The TEB Class D airspace underlies Newark Liberty International Airport's Class B airspace. The control tower was constructed on the east side of the airport by the FAA and went into operation on October 29, 1975. The tower did not have a ground radar system such as the Airport Movement Area Safety System (AMASS). ATCT staffing at the time of the incident included a Front Line Manager action as Tower Supervisor, a local controller, a local control developmental, a ground controller, and a flight data and clearance delivery operator combined to a single controller position. The local controller was conducting on the job training.
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".
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
