The U.S. aircraft register, updated daily
Accidents · NTSB DCA23LA192 · Final report

Learjet INC 60 and Embraer ERJ 190-100 IGW incident near Boston, Massachusetts, February 27, 2023

On February 27, 2023 at about 11:54 pm local time, 2 aircraft, Learjet INC 60 (N280LJ) and Embraer ERJ 190-100 IGW (N179JB), were involved in the same incident near Boston, Massachusetts (Boston-Logan Innternational Ai airport). No one was hurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

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

What the record shows

Date
February 27, 2023 · about 11:54 pm local time · cases in 2023
Place
Boston, Massachusetts · Boston-Logan Innternational Ai · cases near this airport · map
Type
Incident
Injuries
No one was hurt.
Weather
visual conditions (good weather)
Aircraft 1
Learjet INC 60, built 2004
Registration
N280LJ · no longer on the register · serial 60-280
Damage
Not recorded
Flight
Positioning flight · general aviation rules (Part 91)
Aircraft 2
Embraer ERJ 190-100 IGW, built 2005 · all ERJ 190-100 IGWs on the register
Registration
N179JB · no longer on the register · serial 19000006
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative for the Learjet INC 60 final · quoted from the NTSB record

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. Figure 1. Flight tracks of both JetBlue (JBU206) and Hop-a-Jet (HPJ280) with yellow circle indicating incursion area. Figure 2: Screen capture from jump-seat occupant’s video recording showing Lear 60 crossing runway centerline. 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.

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 Embraer ERJ 190-100 IGW final · quoted from the NTSB record

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. Figure 1. Flight tracks of both JetBlue (JBU206) and Hop-a-Jet (HPJ280) with yellow circle indicating incursion area. Figure 2: Screen capture from jump-seat occupant’s video recording showing Lear 60 crossing runway centerline. 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.

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 Learjet INC 60 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway incursion veh/AC/person during takeoff defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Flight crew

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 22,544 hours in all; 2,317 in this make and model; 126 in the last 90 days; 51 in the last 30 days; 16,971 as pilot in command
  • Last flight review: January 11, 2023
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,027 hours in all; 388 in this make and model; 160 in the last 90 days; 55 in the last 30 days; 1,649 as pilot in command
  • Last flight review: June 30, 2022
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Seats: 11
  • Landing gear: retractable
  • Engine 1: P&W Canada PW305A (turbofan); 0 hours total
  • Engine 2: P&W Canada PW305A (turbofan); 0 hours total

The flight

  • Destination: KFXE Fort Lauderdale FL
  • Flight plan: IFR
  • Runway 04L, 7,864 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 330° at 6 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 6,000 ft; a few clouds at 4,600 ft
  • Temperature: 36°F (2°C), dew point 19°F (-7°C)
  • Altimeter: 29.83 inHg
  • Observation at 3:54 pm from BOS

The factual record for the Embraer ERJ 190-100 IGW from the NTSB's investigation tables, in plain English

The NTSB's findings

  • Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on operation

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 7,505 hours in all; 1,673 in this make and model; 71 in the last 90 days; 20 in the last 30 days; 2,817 as pilot in command; 2,726 on instruments
  • Last flight review: May 31, 2021
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 2,280 hours in all; 75 in this make and model; 75 in the last 90 days; 47 in the last 30 days; 985 as pilot in command; 487 on instruments
  • Last flight review: December 28, 2022
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Seats: 20
  • Landing gear: retractable
  • Engine 1: Ama/Expr UNKNOWN ENG; 0 hours total
  • Engine 2: Ama/Expr UNKNOWN ENG; 0 hours total

The flight

  • Departed from: KBNA Nashville TN at 10:05 pm
  • Flight plan: IFR
  • A second pilot was aboard

Documents from the investigation the NTSB's docket: the evidence folder behind the report

7 documents, released by the NTSB on August 3, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - N280LJ PDF, 11 pages View Download
2 Employee Statements Hop-a-jet Captain PDF, 1 page View Download
3 Employee Statements Hop-a-jet Copilot PDF, 1 page View Download
4 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Jetblue PDF, 11 pages View Download
5 Employee Statements - Jetblue Flight Crew PDF, 1 page View Download
6 Employee Statement - Jumpseater PDF, 1 page View Download
7 On Board Video Specialist's Factual Report PDF, 7 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place
Analytics

The whole map of how records connect · these connections as data: /graph/accident/DCA23LA192.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.