The U.S. aircraft register, updated daily
Accidents · NTSB DCA10IA015 · Final report

Boeing MD incident near Charlotte, North Carolina, December 14, 2009

On December 14, 2009 at about 3:46 am local time, a Boeing MD, registered N483A, suffered minor damage in an incident during landing (flare/touchdown) near Charlotte, North Carolina (Charlotte Douglas Intl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 115 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The Captain's failure to initiate a go-around from a Category III approach when satisfactory tracking performance was not maintained below the required altitude resulting in excessive bank angle maneuvers at low altitude. Factors contributing to the incident were: The Captain's decision to execute a Category III autoland approach on a runway without rollout guidance contrary to company Flight Manual guidance, the Captain's decision to deviate from the Category III approach and continue it manually contrary to the company Operating Manual, and the First Officer's failure to call for a go-around when the approach became unstable.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 14, 2009 · about 3:46 am local time · cases in 2009
Place
Charlotte, North Carolina · Charlotte Douglas Intl · cases near this airport · map
Type
Incident
Injuries
No one was hurt; 115 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Boeing MD 82
Registration
N483A · registry record
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

Both pilots indicated that they had set up the navigation systems and briefed to fly an ILS Category III instrument approach to an autoland to runway 36C. The captain stated that,"sometime below 300 feet," he disconnected the autopilot and took manual control of the airplane, noting that the airplane was slightly right of the centerline of the runway with the nose pointed to the left and the airplane was drifting toward the left. As the captain maneuvered to correct the airplane's track, the bank angle aural alert sounded three times, once as the airplane descended below about 300 feet AGL, again at an altitude of about 200 feet AGL, and the last time at about 30-32 feet AGL. During the landing, the right wing tip, right slat and a landing light were damaged. The operator's Flight Manual states, in part, that autolands may be conducted to CAT I / II / III designated runways provided that the procedure does not have a chart note or NOTAM which renders the localizer unusable inside the runways threshold. The 11-5A Jeppesen approach chart for the ILS 36C approach had a note listed on the chart face that stated: IDQG LOC 36C unusable for rollout guidance. Relevant sections of the operator's Operating Manual stated that all Category III approaches are to be flown by the autopilot and to an autoland. In interviews with the MD80 Fleet Training Manager, the MD80 Fleet captain, and an MD80 APD (Aircrew Program Designee), each stated that the operator trains its MD80 crews to autoland all Category III approaches, rather than manually flying the airplane during the final descent to the runway. According to the operator's DC-9 Operating Manual, the following conditions would require a go around from a Category III Approach: 1. Below 300 feet (RA), if satisfactory tracking performance was not maintained. 2. Failure of required airplane or ground equipment prior to DH (Cat II) or prior to touchdown (Cat III). FAA Advisory Circular (AC)120-71A "Standard Operating Procedures for Flight Deck Crewmembers" Appendix 2, states in part: An approach is stabilized when all of the following criteria are maintained from 1000 feet height above touchdown (HAT), or 500 feet HAT in VMC, to landing in the touchdown zone: 1. The airplane is on the correct track. 2. After glide path intercept, or after the FAF, or after the derived fly-off point (per Jeppesen) the pilot flying requires no more than normal bracketing corrections to maintain the correct track and desired profile (3° descent angle, nominal) to landing within the touchdown zone. A stabilized approach means the airplane must be: • At Approach Speed (VREF + additives). • On the proper flight path at the proper sink rate. • At stabilized (spooled up) thrust. These requirements must be maintained throughout the rest of the approach for it to be considered a stabilized approach. If the stabilized approach requirements cannot be satisfied by the minimum stabilized approach heights or maintained throughout the rest of the approach, a go-around was required. The FAA Advisory Circular appendix goes on to state in part that normal bracketing corrections relate to bank angle, rate of descent, and power management and recommends ranges for the various parameters, noting that operating limitations in the approved airplane flight manual must be observed, and may be more restrictive. For bank angle the AC recommends a maximum bank angle permissible during approach is specified in the approved operating manual used by the pilot, and is generally not more than 30°; the maximum bank angle permissible during landing may be considerably less than 30°, as specified in that manual. According to the operator's Flight Manual Supplement,there were six modes of the Ground Proximity Warning System (GPWS)function. Mode 6 provided optional callouts for descent through predefined radio altitudes between 2,500 and 10 feet AGL and excessive roll or bank angle warning. Bank angle warning provided over-banking protection during approach, climb out, and cruise. Additionally, the warning protected against wing or engine strikes during the landing. Further, the operator's DC-9 Operating Manual also stated in part that with the main landing gear compressed, the landing light will strike the runway at approximately eight and one-half degrees of bank, and that excessive bank angles should be avoided at low altitudes. The operator had a no-fault go-around policy. Pilots were told to execute every approach with the presumption that a missed approach was a successful outcome, and asked to plan each approach through the missed-approach procedure and make the decision to land only when all criteria are safely satisfied. According to the operator's Flight Manual, the captain "should give every consideration to a recommendation by another cockpit crewmember that a missed approach be executed." The American Airlines MD80 Fleet Captain told investigators that the first officer could also call for a go around, and did not have to explain why. During post-incident interviews, the first officer stated that during the approach, neither pilot mentioned a go around. The captain stated in his interview that he did not consider a go around.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Dragged wing/rotor/float/other during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation

The aircraft

  • Landing gear: fixed
  • Operator: American Airlines

The flight

  • Departed from: DFW Fort Worth TX at 1:35 am
  • Destination: CLT Charlotte NC
  • Flight plan: IFR
  • Runway 36C, 10,000 ft by 300 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Sky: overcast at 300 ft
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
Passengers110

Documents from the investigation the NTSB's docket: the evidence folder behind the report

30 documents, released by the NTSB on March 15, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Operations - Specialist Report to the Iic PDF, 52 pages View Download
3 Operations - Attachment 1 - Interview Summaries PDF, 18 pages View Download
4 Operations - Attachment 2 - Dispatch Paperwork PDF, 129 pages View Download
5 Operations - Attachment 3 - Aircraft Maintenance and Routing PDF, 10 pages View Download
6 Operations - Attachment 4 - Charlotte, Nc Charts PDF, 5 pages View Download
7 Operations - Attachment 5 - Pilot Statements PDF, 3 pages View Download
8 Operations - Attachment 6 - Clt Weather PDF, 3 pages View Download
9 Operations - Attachment 7 - Clt Tower Facility Log PDF, 3 pages View Download
10 Operations - Attachment 8 - Pilot Monthly Schedules PDF, 5 pages View Download
11 Operations - Attachment 9 - Post Incident ILS Readings PDF, 6 pages View Download
12 Operations - Attachment 10 - Clt Traffic Count PDF, 2 pages View Download
13 Operations - Attachment 11 - Crew Flight Times PDF, 4 pages View Download
14 Operations - Attachment 12 - Pilot Training Records PDF, 11 pages View Download
15 Operations - Attachment 13 - Aa F4 Message Regarding Localizer Rollout PDF, 2 pages View Download
16 Operations - Attachment 14 - Autopilot Callout PDF, 2 pages View Download
17 Operations - Attachment 15 - Flight Confidence Checks PDF, 8 pages View Download
18 Operations - Attachment 16 - Bank Angle Alert PDF, 2 pages View Download
19 Operations - Attachment 17 - Standard Callouts PDF, 3 pages View Download
20 Operations - Attachment 18 - Stable Approach Criteria PDF, 2 pages View Download
21 Operations - Attachment 19 - ASRS Search Results PDF, 3 pages View Download
22 Operations - Attachment 20 - Operation Specifications C60 PDF, 10 pages View Download
23 Operations - Attachment 21 - Gear Crossing Height PDF, 8 pages View Download
24 Operations - Attachment 22 - Missed Approach - Go-around PDF, 6 pages View Download
25 Operations - Attachment 23 - Clt ILS Critical Areas PDF, 2 pages View Download
26 Operations - Attachment 24 - Weight and Balance PDF, 13 pages View Download
27 Cockpit Voice Recorder 12 - Specialist's Factual Report PDF, 4 pages View Download
28 FDR Plots 1 PDF, 1 page View Download
29 FDR Plots 2 PDF, 1 page View Download
30 FDR Plots 3 PDF, 1 page View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/DCA10IA015.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.