Jetblue E190 at Boston on Feb 27th 2023, collision on runway averted by late go around

Last Update: August 4, 2023 / 10:59:13 GMT/Zulu time

Bookmark this article

Photo of Jetblue N179JB, Embraer ERJ-190 — Jetblue N179JB, Embraer ERJ-190 (Photo credit: Anna Zvereva / Flickr / License: CC by-sa)

Incident Facts

Date of incident
Feb 27, 2023

Classification
Report

Airline
Jetblue

Flight number
B6-206

Departure
Nashville, United States

Destination
Boston, United States

Aircraft Registration
N179JB

Aircraft Type
Embraer ERJ-190

ICAO Type Designator
E190

A Jetblue Embraer ERJ-190, registration N179JB performing flight B6-206 from Nashville,TN to Boston,MA (USA), was on final approach to Boston's runway 04R cleared to land on the runway.

A business jet had been cleared to line up and wait on crossing runway 09, the crew of Embraer already cleared to land heard that clearance, acknowledge the clearance and proceeded onto the runway, however, commenced their takeoff run without clearance.

When the tower controller noticed the business jet had begun their takeoff run, he instructed the Embraer to go around.

The NTSB reported the Embraer was already over the runway 04R when they reached their lowest and closest point at about 30 feet AGL after initiating the go around. An observer in the cockpit videotaped the approach, the NTSB provided a single frame out of the video (see below).

On Aug 4th 2023 the NTSB released their final report concluding the probable cause of the incident was:

The Hop-a-Jet flight crew taking off without a takeoff clearance which resulted in a conflict with a JetBlue flight that had been cleared to land on an intersecting runway.

The NTSB analysed:

JetBlue’s flight 206 (JBU206) flight crew initiated a go-around while over runway 04R due to Hop-a-Jet flight 280 (HPJ280) taking off without a takeoff clearance from runway 09 at Boston Logan International Airport (BOS).

Runways 04R and 09 at BOS are intersecting runways. The BOS tower controller had instructed the pilot of HPJ280 to line up and wait (LUAW) on runway 09 while JBU206 had been cleared to land on runway 04R. HPJ280’s flight crew read back the controller’s instructions to LUAW, however they began the takeoff-roll instead. The airport surface detection equipment, model X (ASDE-X) alerted, and the controller issued go-around instructions to JBU206.

JBU206’s flight crew initiated a go-around while over runway 04R, prior to reaching the intersection with runway 09. The closest proximity between both airplanes occurred when JBU206 was about 30ft AGL during the landing flare, close to the point where both runways intersected, see figure 1. A video file taken by the occupant of the flight deck observer seat was provided to the NTSB and a screen capture from the video is shown in figure 2.

The captain of HPJ280 said that they had received clearance to cross runway 4L on taxiway E, and then take taxiway Mike, to Runway 9. On taxiway M he said, “they had heard a clearance that seems to be Line Up and Wait." He further stated that “he probably responded to the clearance, but in his mind, they were cleared for takeoff.” He said they performed the takeoff at 18:55 local time, and during cruise they received a message from ATC providing them with a phone number to call upon landing. After landing at FXE, BOS tower told them that they had taken off without authorization and caused an airplane that had been cleared to land on runway 04 to execute a go-around, passing about 400' above them.

The first officer of JBU206 was the pilot flying, and they were on the ILS runway 04R approach. The captain of JBU206 said they had been cleared to land and had completed the landing checklist. On the tower frequency, they heard that an aircraft had been given LUAW instructions. As they entered the flare after crossing the threshold of runway 04R, about 30 feet above the ground, he saw an airplane cross 04R on runway 09 from his left and going to the right but could not estimate how far away the airplane was.