Atlas Air Boeing 747 400F accident
Boeing 747 400F · Accident: flight control system malfunction/failure on approach
From Rio de Janeiro Galeão – Tom Jobim International Airport (SBGL) to Miami International Airport (MIA)
Event
- NTSB case
- DCA10CA061
- 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
- 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
Boeing 747 400F
- Aircraft type
- Boeing 747
- 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
- N498MC
- Operator
- Atlas Air
- Onboard fatalities
- Unknown
- Route
- From Rio de Janeiro Galeão – Tom Jobim International Airport (SBGL), Rio de JaneiroTo Miami International Airport (MIA), Miami, FL
- 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 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
- Approach
- 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
- Flight control system malfunction/failure
- 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 structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On May 17, 2010, an Atlas Air Cargo Boeing 747-400F, N498MC, lost a section of the left fore-flap while on approach to Miami International Airport (KMIA), Miami, Florida. The airplane was substantially damaged when the flap portion impacted the fuselage. There were no injuries to the flight crew and the airplane landed without further incident. The cargo flight originated from Rio de Janeiro-Galeão-Antonio Carlos Jobim International Airport (BGL), Rio de Janeiro, Brazil.
According to the operator, the flight crew heard and felt a large impact after 30 degree flaps was selected during the approach. Postflight inspection revealed that approximately twelve feet of the right wing inboard fore flap was missing and had caused substantial damage to the aft fuselage.
The separated section of the fore flap was recovered and examined. The examination revealed that a large portion of the enamel was missing from the fore flap attachment fitting of the carriage assembly and that there was a large amount of contamination and grease buildup around the lubrication fitting. Extensive corrosion byproducts covered up the lubrication passage in the attachment, which prevented passage of grease to the bearing, causing extensive corrosion in the bore and propagated by fatigue before final ductile separation.
Probable cause
impact of the fore flap with the aft fuselage after fatigue failure of the right wing fore flap carriage assembly attachment fitting at position 6.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA10CA061
- Event ID
- 20100520X02527
- Case number
- DCA10CA061
- 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: f9f11e169257182f42abe23406044eb57a61229ed88666e0933cb8b2fc24e8b6; retrieved 2026-09-15T14:08:58.316Z.