The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB OPS07IA005 · Final report

Piaggio Industrie P180 and Cirrus Design Corp. SR-22 incident near Teterboro, New Jersey, June 17, 2007

On June 17, 2007 at about 5:20 pm local time, 2 aircraft, Piaggio Industrie P180 (N152SL) and Cirrus Design Corp. SR-22 (N6026K), were involved in the same incident near Teterboro, New Jersey. No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 17, 2007 · about 5:20 pm local time
Place
Teterboro, New Jersey · map
Type
Incident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Piaggio Industrie P180
Registration
N152SL · registry record
Damage
Minor damage
Flight
Flight · charter and air-taxi rules (Part 135)
Aircraft 2
Cirrus Design Corp. SR-22
Registration
N6026K · registry record
Damage
Not recorded
Flight
Executive or corporate flight · general aviation rules (Part 91)

The NTSB's narrative for the Piaggio Industrie P180 final · quoted from the NTSB record

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."

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Cirrus Design Corp. SR-22 final · quoted from the NTSB record

On June 17, 2007, at 1320 EDT (1720 UTC), a runway incursion occurred at Teterboro Airport (TEB), New Jersey involving Avantair (VRN) flight 152, a P180, and N6026K, an SR22. AT 1319:02, the pilot of VRN152, an IFR departure, advised the tower controller that they were ready to depart from runway 24. The tower controller responded, 'Avantair one five two, runway 24, cleared for takeoff.' At 1319:42, the pilot of N6026K, a VFR departure, advised the tower controller that he was 'ready to go [on runway 19] at [taxiway] bravo.' The tower controller responded, 'Cirrus two six kilo left turn northeast bound maintain at or below one thousand runway 19 at bravo cleared for takeoff.' The pilot of VRN152 saw N6026K on departure roll and applied maximum braking, experienced two blown tires on the main gear, as N6026K rolled past, through the intersection 50 feet in front. VRN152 stopped in the intersection. The tower controller stated that he did not see the incursion, so he did not cancel either takeoff clearance. There were 3 people in the tower cab; the tower/controller-in charge and two developmental controllers who were working clearance delivery, one controller was on break. The two developmental controllers were faced away from the front of the cab and did not see the event. The incident occurred during day VFR conditions (clear sky with 10 miles visibility).

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Piaggio Industrie P180 from the NTSB's investigation tables, in plain English

Pilot

  • Injury: no injuries

The aircraft

  • Landing gear: fixed

The flight

  • Departed from: TEB Teterboro NJ
  • Flight plan: IFR

Weather at the time

  • Wind: from 290° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 84°F (29°C), dew point 55°F (13°C)
  • Altimeter: 29.88 inHg
  • Observation at 12:51 pm from TEB

Injuries

FatalSeriousMinorNone
Crew2

The factual record for the Cirrus Design Corp. SR-22 from the NTSB's investigation tables, in plain English

The aircraft

  • Landing gear: fixed
  • Operator: Cirrus Exchange LLC

The flight

  • Departed from: TEB Teterboro NJ
  • Flight plan: VFR

Injuries

FatalSeriousMinorNone
Crew1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number OPS07IA005.