FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21LA246 · Honda Aircraft Co LLC HA-420

4 Jun 2021 · Kennesaw, GA, United States

Honda Aircraft Co LLC HA-420 · Accident: part(s) separation from aircraft during landing

From Kissimmee Gateway Airport (ISM) to an unrecorded destination

Report a problem

Event

NTSB case
ERA21LA246
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
Event fatalities
Unknown
Ground fatalities
Unknown
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Honda Aircraft Co LLC HA-420

Aircraft type
Honda 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
N10XN
Operator
FlightWorks
Onboard fatalities
Unknown
Route
From Kissimmee Gateway Airport (ISM), Orlando, FLTo not recorded
Aircraft age
About 5 years (built 2016)
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 91: General Aviation
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 · landing roll
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
Part(s) separation from aircraft
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The accident flight and approach to the airport were normal. After the airplane touched down on the runway, the pilot applied the brakes; however, there was no braking action. The pilot called out that they had “no brakes” and elected to pull the emergency brake. The airplane began to skid, continued off the left side of the runway, completed a 180° turn, and came to rest in the grass. During the accident sequence, the right main landing gear collapsed, which resulted in substantial damage to the right wing.

The left main landing gear wheel was located about 225 ft from the main wreckage. Examination of the axle revealed that there was damage to the bottom threads of the axle and partial thread damage on the nut that secured the wheel to the axle. The individual parts of the left wheel retention stack (axle nut, retention key, and hubcap) were found intact inside the wheel hubcap. The retention key, which contained the locking tabs, was still safety wired to the axle nut. The airplane discrepancy log indicated that the left main landing gear wheel assembly was replaced the morning of the accident due to a discrepancy the pilot wrote up the day before the accident.

The mechanic who performed the work reported that during the installation of the left wheel assembly, the locking tab did not engage into the axle, so he removed and reinstalled the wheel assembly, which then “slid into place much easier.” In addition, the mechanic reported the jack he used to perform the maintenance was not the jack specified in the maintenance manual for the procedure. Although the mechanic stated the left main wheel assembly was installed correctly, it likely was not installed properly as indicated by the minimal damage to the securing nut and to the axle, which likely occurred when the axle contacted the runway surface after the wheel departed the airplane. Additionally, a study performed comparing the jack the mechanic used to the jack specified in the maintenance procedure indicated that it was possible for the unapproved jack to interfere with the proper reseating of the wheel assembly on the axle during installation. Further, the mechanic who performed the maintenance had not received specific training on the airframe. In summary, given the limited damage to the wheel assembly, the mechanic’s lack of airplane specific maintenance training, and his use of an improper jack for the maintenance, it is likely the mechanic installed the wheel assembly improperly, which resulted in the wheel separating from the airplane.

Probable cause

The mechanic’s improper installation of the left main wheel assembly.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21LA246
Event ID
20210610103242
Case number
ERA21LA246
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: fcfc69a9e91c3e7368762daf1b028f98a6ed695ad10436c556351dd7c26d307a; retrieved 2026-09-16T14:08:59.810Z.