FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

US Airways Flight 1556

24 Feb 2012 · Millville, NJ, United States

Airbus A321 112 · Accident: turbulence encounter on approach

From Fort Lauderdale Hollywood International Airport (FLL) to Philadelphia International Airport (PHL)

Report a problem

Event

NTSB case
DCA12FA046
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
Instrument Meteorological Cond

Airbus A321 112

Aircraft type
Airbus A321
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
N162UW
Operator
U.S Airways
Onboard fatalities
Unknown
Route
From Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, FLTo Philadelphia International Airport (PHL), Philadelphia, PA
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
Turbulence encounter
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The flight encountered severe turbulence and two lightning strikes while the flight was level at 13,000 feet in instrument meteorological conditions. The seatbelt sign had been illuminated since the passing through 18,000 feet during the descent and was on at the time of the encounter. Prior to the turbulence, a passenger had ignored the seatbelt sign and entered the lavatory, unbeknownst to the flight attendants, who were preparing the cabin for landing. At the time of the turbulence encounter, the passenger was exiting the lavatory and was severely injured. Inflight turbulence and convection advisories had been forecasted for the area where the flight encountered the turbulence. There was a convective SIGMET for severe thunderstorms and for occasional turbulence between 16,000 feet and FL 280. In addition, there were several pilot reports of turbulence in the area.

Probable cause

an encounter with convective turbulence that resulted in injury to a passenger who was not seated when the seatbelt sign was illuminated.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA12FA046
Event ID
20120302X22622
Case number
DCA12FA046
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, damage. 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: 314b04b7c9ca3a86ceaad40f32407aac1ccca4a19b2a8b27090428cfe3a9697d; retrieved 2026-09-15T17:21:58.255Z.