FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Jet It Honda Jet HA-420 accident

9 Mar 2022 · Pittsburgh, PA, United States

Honda Jet HA-420 · Accident: runway excursion during landing

From Teterboro Airport (TEB) to an unrecorded destination

Report a problem

Event

NTSB case
ERA22LA150
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
Accident
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
0
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
Instrument Meteorological Cond

Honda Jet HA-420

Aircraft type
Honda Jet HA-420
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
N903JT
Operator
Jet It
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo not recorded
Aircraft age
About 1 year (built 2021)
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
Landing
Defining eventThe 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
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

At the time of the approach and landing, a Braking Action Advisory was in effect and a field condition NOTAM reported slush on the landing runway. The airplane was flying 11 knots faster than the prescribed approach speed as it descended through 1,000 ft with the engines at idle. The pilots continued the instrument approach and visually acquired the runway environment about 100 ft above ground level. The airplane crossed the runway threshold 9 knots faster than VREF (landing reference speed), and touched down 893 ft past the touchdown zone at a speed that was 3 knots faster than the speed assumed by the airplane flight manual (AFM) landing distances. The airplane began to decelerate; however, the captain called for maximum braking when he detected the deceleration to be insufficient to stop the airplane on the remaining runway. He applied the emergency brake and steered to the left to try to stay on the airport property. The airplane skidded sideways, departed the end of the runway, and travelled tail-first over the edge of a steep incline, which resulted in substantial damage to the wings and fuselage. When the airplane descended below 1,000 ft on the final approach segment of the flight, the thrust levers were at idle, contrary to the operator’s stabilized approach requirement. The operator’s standard operating procedures required that if an approach became unstabilized below 1,000 ft, the flight crew was to initiate a go-around and missed approach procedure. The crew did not initiate a go-around, but instead continued the approach, which resulted in a fast and long landing. This increased the runway length required to stop from that predicated on a nominal touchdown location. Further exacerbating the long and fast landing was the captain’s decision during the landing roll to fully engage the emergency brake. Per the AFM, this action would result in the anti-skid feature not operating and would increase the wet runway landing distance by 100%. Postaccident examination of both main landing gear tires revealed evidence of reverted rubber hydroplaning, consistent with a locked wheel skid. It is likely that the full application of the emergency brake put the airplane into a locked-wheel skid and reduced the braking performance of the tires. Postaccident examination of the braking system revealed no evidence of any preimpact anomalies or malfunctions that would have precluded normal operation. Performance calculations revealed that the wheel braking friction coefficient achieved during the landing was lower than that implied in the wet runway landing distances recommended by the AFM and specified in the FAA Runway Condition Assessment Matrix (RCAM) guidance for wet runways, consistent with the findings in other wet runway landing overruns investigated by the NTSB. Performance calculations and postaccident simulations of the airplane’s stopping performance indicated that even with the longer-than-nominal touchdown point and 3-knot fast airspeed at touchdown, the airplane might have stopped before the end runway had it achieved the wet runway wheel braking friction coefficient implied by the AFM wet runway landing distance recommendation, and would have stopped about 850 ft before the end of the runway had it achieved the wheel braking friction coefficient specified by the RCAM. Conversely, even with the 3-knot fast airspeed at touchdown and the lower friction coefficient actually achieved during the landing roll, the airplane would still have stopped on the runway had it touched down at the nominal touchdown point.

Probable cause

The flight crew's continuation of an unstable approach, which resulted in a long landing on a contaminated runway. Contributing to the outcome was the captain’s full application of the emergency brake, which resulted in hydroplaning and a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA150
Event ID
20220310104756
Case number
ERA22LA150
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • 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, cause areas. 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: 2e78dbd6723e161e04f6f662c86df4893e0660f3ec470799a4f745cbec8b0242; retrieved 2026-09-16T15:01:49.924Z.