FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Avantair Piaggio Industrie P180 incident

17 Jun 2007 · Teterboro, NJ, United States

Piaggio Industrie P180 and Cirrus Exchange Cirrus Design Corp. SR-22 · Incident: near collision between aircraft during takeoff

Report a problem

Event

NTSB case
OPS07IA005
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 · Piaggio Industrie P180

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
N152SL
Operator
Avantair
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo Martin State Airport (MTN), Baltimore, MD
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
Takeoff · rejected 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
Minor

Aircraft 2 · Cirrus Design Corp. SR-22

Aircraft type
Cirrus SR-22
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
N6026K
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo not recorded
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 · roll/run
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

  • Control tower › Improper

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

NTSB narrative

On June 17, 2007, at 1720 Coordinated Universal Time, 1320 Eastern daylight time, Avantair (VRN) flight 152, a Piaggio P180 and N6026K, a Cirrus SR-22, nearly collided in the intersection of runways 19 and 24 at Teterboro Airport (TEB), Teterboro, New Jersey. VRN152 was operating under 14 CFR Part 135 as a domestic non-scheduled on-demand air taxi on an instrument flight plan destined for Martin State Airport, Baltimore, Maryland (MTN). VRN152 was not carrying passengers at the time. N6026K was operating under 14 CFR Part 91 and was on a visual flight rules flight plan. There were no injuries reported to the any of the crew or passengers on either aircraft. VRN152 reported no damage to the aircraft; however, the tires, wheels and brake assemblies had to be replaced post incident. There was no damage to N6026K.

VRN152 was assigned transponder code 7153; N6062K was assigned transponder code 0330.

At 1719:02, VRN152 transmitted to the Teterboro tower controller, "and Avantair one five two is ready ah for [runway] two four." The tower controller replied, "Avantair one five two, runway two four, cleared for takeoff." The pilot acknowledged the clearance. VRN152 departed from the approach end of runway 24.

At 1719:42, the pilot of N6026K transmitted to the same tower controller and said, "n two six kilo is ready to go [on runway 19] at [taxiway] bravo." The tower controller replied, "Cirrus two six kilo left turn northeast bound maintain at or below one thousand, runway one niner cleared for takeoff." The pilot responded, "ok left turn northeast bound and at or below one thousand ah cleared to go two kilo six." At 1720:28, N6026K transmitted, "and two six kilo we have an open door we're just gonna stop here for one second if that's possible." The tower controller did not acknowledge this transmission.

During the following 18 seconds, according to the VRN152 pilot's statement, the pilot of VRN152 observed N6026K on a potential collision course and applied maximum braking and retarded engine power. The ground speed of VRN152 was approximately 106 knots. With the brakes locked up, and as the two aircraft approached one another, the pilot of VRN152 applied right rudder in an attempt to minimize the impact and hit N6026K in the tail section vice a direct broadside hit at the wings. The pilot of VRN152 stated that his aircraft passed "what seemed like just feet behind the Cirrus and it took a few moments" for the pilot to realize he had not collided with the Cirrus. VRN152 continued down runway 24, where the pilot was able to maintain directional control until the tail slid out and the aircraft slid, coming to a stop approximately 3800 feet from the approach end of the runway, facing approximately on a north heading.

The pilot of N6026K recalled crossing the runway 24 intersection with 40 to 50 knots of airspeed indicated, noticed an aircraft off to his right and as he looked further, noticed it was in full braking mode and beginning to turn sideways on the runway. At this point, the pilot of N6026K was committed to his own departure and followed through with rotation. N6026K did not recall whether he slowed down or came to a complete stop during this departure evolution.

The tower controller stated he was distracted and did not observe the event, therefore he did not cancel the takeoff clearance to either aircraft; however, a comment he made alerted the other controllers in the tower cab to observe the incident.

At 1720:46, Teterboro tower transmitted "avantair one fifty two you you alright." At 1720:48, VRN 152 responded "yeah we're fine."

Probable cause

The TEB tower local controller's failure to ensure separation between two aircraft departing on intersecting runways.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS07IA005
Event ID
20070618X00759
Case number
OPS07IA005
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, 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: 92414c8d2cab1973df0ca1ffe4d7cf01d108c10aaeafcd2531280b26f1f77700; retrieved 2026-09-18T14:43:50.731Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: destination. The narrative states VRN152 was "on an instrument flight plan destined for Martin State Airport, Baltimore, Maryland (MTN)".