FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA233 · Hughes Charles R ZODIAC 601XL

7 May 2013 · Meriden, CT, United States

Hughes Charles R ZODIAC 601XL · Accident: loss of control on ground during landing

From Meriden Markham Municipal Airport (MMK) to Meriden Markham Municipal Airport (MMK)

Report a problem

Event

NTSB case
ERA13CA233
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
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

Hughes Charles R ZODIAC 601XL

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
N418CM
Onboard fatalities
Unknown
Route
From Meriden Markham Municipal Airport (MMK), Meriden, CTTo Meriden Markham Municipal Airport (MMK), Meriden, CT
Aircraft age
Not recorded
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
Loss of control on ground
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he landed with a tailwind and that the airplane touched down farther down the runway than usual. When the pilot applied brakes to exit the runway onto the taxiway, the tires skidded, and the airplane pivoted to the left before coming to rest inverted. Postaccident examination revealed substantial damage to the left and right wings and to the vertical stabilizer. The pilot reported that there were no mechanical anomalies with the airplane. He further stated that he was fatigued, had “rushed” the landing approach, and had not taken time to properly evaluate the wind conditions prior to landing.

Probable cause

The pilot's decision to land with a tailwind and his failure to maintain aircraft control during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA233
Event ID
20130509X72539
Case number
ERA13CA233
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. 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: bfd5851495f2a486a8a1f9e39befd9e026c4c428fbf59604a6a761c7dc947493; retrieved 2026-09-15T21:29:18.860Z.