USAir Flight 1016
Douglas DC-9-31 · Crashed on approach due to microburst induced windshear and spatial disorientation
From Columbia Metropolitan Airport (CAE) to Charlotte Douglas International Airport (CLT)
Event
- NTSB case
- DCA94MA065
- 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
- 37 · all aircraft and ground
- Ground fatalities
- 0
- Occupants
- 57
- Survivors
- 20
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 20
- 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
- Instrument Meteorological Cond
Douglas DC-9-31
- Flight
- US1016
- Aircraft type
- Douglas DC-9
- 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
- N954VJ
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Columbia Metropolitan Airport (CAE), Columbia, SCTo Charlotte Douglas International Airport (CLT)
- 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 · IFR missed approach
- First occurrenceThe 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
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Atc personnel(lcl/gnd/clnc) › Unsafe/hazardous condition warning, inadequate
- Flightcrew › Aircraft handling, improper
- Flightcrew › In-flight planning/decision, improper
- Flightcrew › Weather evaluation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
USAir Flight 1016 was a regularly scheduled domestic passenger flight in the southeastern United States, between Columbia, South Carolina, and Charlotte, North Carolina. On July 2, 1994, the McDonnell Douglas DC-9-31 operating the flight encountered heavy thunderstorms and microburst-induced windshear while attempting to land, and crashed into heavy trees and a private residence near the airport. The crash and ensuing fire caused 37 fatalities and seriously injured 20 others.
History of the flight
On Saturday, July 2, 1994, the McDonnell Douglas DC-9, that was flying as USAir Flight 1016 departed Columbia Metropolitan Airport at 18:15 EDT for the 35-minute flight to Charlotte/Douglas International Airport. The crew consisted of Captain Michael R. Greenlee (38), First Officer James P. "Phil" Hayes (41), and three flight attendants. There were 52 passengers (including two infants) on board.
The flight was uneventful until the approach to Charlotte, where several severe thunderstorms were in the vicinity of the airport. At 18:38, Flight 1016 was cleared by Charlotte approach control for an instrument landing system (ILS) approach to Runway 18R (now 18C), with Hayes at the controls in heavy rain. The flight switched over to the local tower controller that was handling landings for 18R, and at 18:39, the controller gave the crew clearance to land. Captain Greenlee asked the controller for a weather report from the plane ahead of Flight 1016, a Fokker 100 that had just landed on 18R. The tower told Flight 1016 that the Fokker pilot reported "smooth sailing." In post-crash interviews, passengers and flight attendants told the NTSB that the flight seemed normal until the plane entered the heavy rain on final approach.
At 18:40, a tower controller issued a windshear warning to all aircraft, but on a different radio frequency than that used by Flight 1016. About a minute later, as Flight 1016 was on final approach, the captain, realizing that his aircraft was in a serious predicament, attempted to abort the landing by instructing the first officer to "take it around, go to the right." The captain then radioed the control tower and stated "USAir ten sixteen's on the go"; the tower acknowledged the missed approach and cleared Flight 1016 to climb to 3000 feet. The plane struggled to climb in the severe weather conditions, veered to the right and rapidly descended. The flight crew desperately tried to control the airplane as it plummeted toward the ground. It was later determined that the windshear alert system did not alert the crew with a red indicator and aural warning because of a software discrepancy that lowered the sensitivity while the flaps were in transit from 40 to 15 degrees during the go-around procedure. A Honeywell engineer stated that the pilots should have received a warning eight to nine seconds before impact.
Crash
At 18:42 EDT, the DC-9 touched down in a field within the airport boundary, about 0.5 mi from the threshold of Runway 18R. It then crashed through the airport fence and impacted several trees, breaking apart while skidding down a residential street that was on the airport boundary. The plane broke into four major sections, and the front 40 ft, including the cockpit and the unoccupied first class passenger cabin, came to rest in the middle of Wallace Neel Road. The rear section of the fuselage, including the tail and the rear-mounted engines, came to rest in the carport of a house.
Of the 52 passengers, 37 died from blunt force trauma, burns from the fire or carbon monoxide inhalation. An additional 14 passengers suffered serious injuries, and one had minor injuries. Of the five crew members, both pilots suffered minor injuries, two flight attendants were seriously injured and the remaining flight attendant sustained minor injuries. No one on the ground was injured.
The airport's previous major incident occurred on September 11, 1974, when Eastern Air Lines Flight 212, also a DC-9, crashed during approach, killing 72.
Investigation and cause
Investigation and response
The NTSB immediately dispatched an investigation team, which recovered the CVR and FDR from the plane's wreckage. After a lengthy investigation, the NTSB concluded that a microburst generated by the thunderstorm over the airport at the time of the crash was the probable cause of the accident. The NTSB listed these contributing factors:
The flight crew's decision to continue an approach to an area where a microburst was likely.
The failure of the flight crew to recognize wind shear quickly (exacerbated by an error in the wind shear alert software; the wind shear alert system should have warned them about 8–9 seconds prior to impact)
The failure of the flight crew to establish proper pitch and engine power that would have brought them out of the wind shear
The lack of timely weather information by air traffic control to the crew of Flight 1016
Text from the Wikipedia article “USAir Flight 1016” (revision 1359881759, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
THE AIRPLANE COLLIDED WITH TREES AND A PRIVATE RESIDENCE SHORTLY AFTER THE FLIGHTCREW EXECUTED A MISSED APPROACH FROM THE RWY 18R ILS. FLIGHTCREW WAS NOT PROVIDED UPDATED WX INFO IN ATIS;WX REFLECTED THUNDERSTORM & RAINSHOWER. TERMINAL DOPPLER WX RADAR NOT INSTALLED AT ARPT AS SCHEDULED; WOULD HAVE PROVIDED CONTROLLERS WITH INFO ABOUT SEVERITY OF WX, AND INFO WOULD HAVE BEEN BENEFICIAL TO FLIGHTCREW. INADEQ ATC PROCEDURES, BREAKDOWN IN COMM IN TOWER, PREVENTED FLIGHTCREW FROM RECEIVING ADDITIONAL CRITICAL INFO ABOUT ADVERSE WX OVER ARPT & ALONG APPROACH PATH. FLIGHT ENCOUNTERED WINDSHEAR OF 61 KTS OVER A 15 SEC PERIOD. INADEQ COMPUTER SOFTWARE DESIGN IN THE AIRPLANE'S ON-BOARD WINDSHEAR DETECTION SYSTEM PREVENTED FLIGHTCREW FROM RECEIVING MORE TIMELY WINDSHEAR ALERT. 1ST OFFICER INITIALLY ROTATED TO PROPER 15 DEG NOSE-UP ATTITUDE DURING MISSED APPROACH. HOWEVER, THRUST WAS SET BELOW STANDARD GO-AROUND EPR LIMIT OF 1.93, PITCH ATTITUDE REDUCED TO 5 DEG NOSE DOWN BEFORE FLIGHTCREW RECOGNIZED DANGEROUS SITUATION. FAA'S POI, USAIR'S MANAGEMENT, WERE AWARE OF INCONSISTENCIES IN FLIGHTCREW ADHERENCE TO OPERATING PROCEDURES WITHIN THE AIRLINE; HOWEVER, CORRECTIVE ACTIONS HAD NOT RESOLVED THIS PROBLEM.
Probable cause
1) THE FLIGHTCREW'S DECISION TO CONTINUE AN APPROACH INTO SEVERE CONVECTIVE ACTIVITY THAT WAS CONDUCIVE TO A MICROBURST; 2) THE FLIGHTCREW'S FAILURE TO RECOGNIZE A WINDSHEAR SITUATION IN A TIMELY MANNER; 3)THE FLIGHTCREW'S FAILURE TO ESTABLISH AND MAINTAIN THE PROPER AIRPLANE ATTITUDE AND THRUST SETTING NECESSARY TO ESCAPE THE WINDSHEAR; AND 4) THE LACK OF REAL-TIME ADVERSE WEATHER AND WINDSHEAR HAZARD INFORMATION DISSEMINATION FROM AIR TRAFFIC CONTROL, ALL OF WHICH LED TO AN ENCOUNTER WITH AND THE FAILURE TO ESCAPE FROM A MICROBURST-INDUCED WINDSHEAR THAT WAS PRODUCED BY A RAPIDLY DEVELOPING THUNDERSTORM LOCATED AT THE APPROACH END OF RUNWAY 18R. CONTRIBUTING TO THE ACCIDENT WERE: 1) THE LACK OF AIR TRAFFIC CONTROL PROCEDURES THAT WOULD HAVE REQUIRED THE CONTROLLER TO DISPLAY AND ISSUE AIRPORT SURVEILLANCE RADAR (ASR-9) WEATHER INFORMATION TO THE PILOTS OF FLIGHT 1016; 2) THE CHARLOTTE TOWER SUPERVISOR'S FAILURE TO PROPERLY ADVISE AND ENSURE THAT ALL CONTROLLERS WERE AWARE OF AND REPORTING THE REDUCTION IN VISIBILITY AND RUNWAY VISUAL RANGE VALUE INFORMATION, AND THE LOW LEVEL WINDSHEAR ALERTS THAT HAD OCCURRED IN MULTIPLE QUADRANTS; 3) THE INADEQUATE REMEDIAL ACTIONS BY USAIR TO ENSURE ADHERENCE TO STANDARD OPERATING PROCEDURES; AND 4) THE INADEQUATE SOFTWARE LOGIC IN THE AIRPLANE'S WINDSHEAR WARNING SYSTEM THAT DID NOT PROVIDE AN ALERT UPON ENTRY INTO THE WINDSHEAR. (NTSB REPORT AAR-95/03)
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: USAir Flight 1016
- Article
- USAir Flight 1016
- Revision
- 1359881759 · 2026-06-17 · retrieved 2026-09-18
- Wikidata
- Q7875834
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA94MA065
- Event ID
- 20001206X01727
- Case number
- DCA94MA065
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "USAir Flight 1016" (page 1922494, revision 1359881759); merged with NTSB case DCA94MA065 (events / aircraft)
- Date
- NTSB record DCA94MA065: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record DCA94MA065
- Map position
- NTSB record DCA94MA065: events decimal coordinates
- Aircraft, operator and route
- NTSB record DCA94MA065: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record DCA94MA065: operated under Part 121: Air Carrier
- Fatalities
- NTSB record DCA94MA065: NTSB API totalFatal
- Ground fatalities
- NTSB record DCA94MA065: NTSB API ongroundFatal
- Summary
- Wikipedia infobox: summary
Source notes (4)
- One occurrence in two sources, merged: the Wikipedia article "USAir Flight 1016" and NTSB case DCA94MA065, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- 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.
- The NTSB's operator name is blank for N954VJ; the operator shown is the name the NTSB's other records give its FAA operator code, USAA.