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

Honda Aircraft CO LLC HA-420 accident near Orlando, Florida, January 28, 2024

On January 28, 2024 at about 9:23 pm local time, a 2019 Honda Aircraft CO LLC HA-420, registered N103JT, was substantially damaged in an accident during landing (landing roll) near Orlando, Florida (Orlando International Airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 4 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 failure of the pilot flying to maintain directional control after touchdown with wind gusts that exceeded the airplane’s crosswind limitation. Contributing to the accident were the flightcrew’s continued approach to the runway despite the consistent wind gust crosswind component that exceeded the airplane’s published crosswind limitation, and their incorrect wind gust crosswind calculation in flight.

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

What the record shows

Date
January 28, 2024 · about 9:23 pm local time
Place
Orlando, Florida · Orlando International Airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Honda Aircraft CO LLC HA-420 NO SERIES, built 2019 · all HA-420s on the register
Registration
N103JT · registry record · serial 42000163
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

The on-demand air taxi flight proceeded to the destination airport and, about 1 hour and 22 minutes before landing, the flight crew reviewed the destination airport automated terminal information service (ATIS), which indicated the wind was from 270° at 14 kts, gusting to 24 kts. The cockpit voice recorder (CVR) recorded the crew discussing the crosswind component of the winds reported on the ATIS, the aircraft operating limitations, company procedures, and an alternate airport, but the pilot flying (PF) elected to continue to the planned destination airport. About 16 minutes before the airplane touched down, when it was about 39 nautical miles (nm) from the destination airport, the PF advised the pilot monitoring (PM) that he checked the airport’s automated surface observing system (ASOS) and reported the wind velocity was currently at 270° at 13-14 kts. While on final approach, about 1.2 nm from the approach end of runway 36L, the tower controller advised that the wind was from 290° at 19 kts, gusting to 24 kts. The PF continued the approach and just about when the airplane was at touchdown the controller broadcast on the frequency for another airplane that was on approach that the wind was from 290° at 20 knots, gusting to 24 kts. After the airplane touched down, it began drifting to the left side of the runway. The PF applied left aileron control input, deployed the speedbrake, and applied right rudder; however, the airplane departed the runway and impacted a frangible runway distance-remaining sign. The PF then corrected the airplane to the right, returned it to the runway, and taxied off onto a taxiway, where the pilot stopped the airplane and evacuated. Postaccident inspection of the airplane revealed substantial damage to the left wing’s forward spar in the area that impacted the sign. The rudder and aileron trims were found in the neutral position. The operator reported there was no preimpact mechanical failure or malfunction with the airplane that would have caused the runway excursion. Although the PF reported about 16 minutes before touchdown that he received the ASOS observations for the previous 20 minutes and stated to the PM that the crosswind was at 13 or 14 kts, with the wind from 270° at 13 kts, a review of the 14 previous 5-minute ASOS observations revealed that gusts were reported in all but 2 of the 14 observations. The PF’s reference specifically to the wind being from 270° at 13 kts corresponded to an observation that also reported gusts to 24 kts, which occurred about 23 minutes before the airplane touched down. That gust value exceeded the airplane’s published crosswind limitation of 20 kts. The gust values at the destination airport consistently exceeded the airplane’s published crosswind limitation for the majority of the 5-minute ASOS observations in 1 hour 23 minutes preceding the accident. These conditions should have necessitated either an earlier diversion to an alternate airport that was more aligned with the wind or a go-around during short final approach after the flight crew was informed, when the airplane was about 1.2 nm from the runway threshold, that the wind was gusting above the published crosswind limitation. The PF chose to continue with the landing and, due to a crosswind gust, failed to maintain directional control of the airplane after landing. The PF also did not incorporate the gust values into the crosswind calculations about 16 minutes before the accident, which likely influenced his decision to continue the approach.

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

What happened, in order

  1. Loss of control on ground during landing (landing roll) defining event
  2. Runway excursion during landing (landing roll)
  3. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Personnel issues › Task performance › (general) › (general) › Pilot
  • Personnel issues › Action/decision › Action › Lack of action › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 4,520 hours in all; 269 in this make and model; 56 in the last 90 days; 39 in the last 30 days; 3,216 as pilot in command
  • Last flight review: September 28, 2023
  • Medical certificate: Class 1
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 3,408 hours in all; 200 in this make and model; 73 in the last 90 days; 15 in the last 30 days; 1,336 as pilot in command
  • Last flight review: April 26, 2023
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,017.1 hours
  • Last inspection: continuous airworthiness programme, January 9, 2024
  • Maximum gross weight: 10,780 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine 1: General Electric HF-120 (turbojet); 3,356 hours total
  • Engine 2: General Electric HF-120 (turbojet); 3,356 hours total
  • Operator: Gc Aviation

The flight

  • Departed from: FSM Fort Smith AR at 7:24 pm
  • Flight plan: IFR
  • Runway 36L, 12,004 ft by 200 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 270° at 16 knots, gusting 23
  • Visibility: 9 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 48°F (9°C)
  • Altimeter: 29.98 inHg
  • Observation at 4:20 pm from KMCO

Weather report (METAR): KMCO 282120Z 27016G23KT 10SM CLR 21/09 A2998 40 45 800 270/16G23 RMK AO2 T02110089

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers2

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

15 documents, released by the NTSB on April 3, 2026. 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.

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

Other NTSB records under N103JT the same tail number, which may have belonged to a different aircraft at the time

2007-11-28NYC08CA048 · accident near Latrobe, PA · substantial damage · serious injuries

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 documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text 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 ERA24LA100.