Endeavor Airlines Flight 5304
Bombardier Inc CL-600-2C10 · Incident: abnormal runway contact during landing
From Montgomery Regional (Dannelly Field) Airport (MGM) to an unrecorded destination
Event
- NTSB case
- DCA26LA139
- 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
- Incident
- 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
- Airline
- 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
Bombardier Inc CL-600-2C10
- Aircraft type
- Bombardier CL-600
- 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
- N354CA
- Operator
- Endeavor Airlines
- Onboard fatalities
- Unknown
- Route
- From Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, ALTo not recorded
- Aircraft age
- About 24 years (built 2002)
- 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 121: Air Carrier
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- 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
Endeavor Air, Inc. doing business as, Delta Connection, flight 5304, a Mitsubishi Heavy Industries RJ Aviation (formerly Bombardier) CL-600-2C10 (CRJ700), sustained minor damage to both wingtips while attempting to land at Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia. According to the flight crew, the departure and enroute portions of the flight were uneventful. After completing the approach briefing and descent checklist, air traffic control instructed the flight to descend via the HOBTT3 Arrival. While descending through 10,000 ft mean sea level (msl), the crew encountered light turbulence and were instructed to expedite the descent through 4,000 ft msl. The flight was subsequently vectored and cleared for the instrument landing system (ILS) approach to runway 27L. During the approach, about 2,000 ft msl, the first officer (FO), who was serving as pilot monitoring, reported the runway in sight. Through 1,000 ft msl, the turbulence intensified and the captain, who was the pilot flying, disconnected the autopilot. About 100 ft above ground level (agl), the first officer called “Vref plus 10,” and the captain made a minor power adjustment. About 30 ft above the runway’s surface, during the flare, the airplane encountered a gust of wind and ballooned. The airplane then rolled to the right, and the captain initiated a go-around. While attempting to level the wings, he overcontrolled, resulting in the left wing contacting the runway. He subsequently overcontrolled in the opposite direction, resulting in the right wing contacting the ground. Following the go-around, the first officer assumed control and completed an uneventful landing. A surface weather observation taken about 22 minutes after the incident reported wind from 230° at 14 knots, with gusts to 23 knots. With a peak gust reported about 20 minutes before the incident from 210° at 30 knots.
Probable cause
The captain’s inadequate compensation for gusting crosswind wind conditions while attempting to land and a subsequent go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA26LA139
- Event ID
- 20260227202559
- Case number
- DCA26LA139
- 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: a53ae21e5ef3b230dd41d0d2b1ddb3a453b7ddd2f270540f76ef1f29669a7570; retrieved 2026-09-16T20:51:49.835Z.