# Accident 20140313003339A: Airbus Industrie A320-214, Philadelphia, PA, March 13, 2014

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 13, 2014, 18:25 local time
- Place: Philadelphia, PA
- Damage: Substantial damage
- Phase of flight: Takeoff: Rotation
- Operating rules: Air carrier (Part 121)
- Operator: USAA
- Location: 39.8606° N, 75.2739° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.8606&lon=-75.2739&mi=10
- Aircraft: N113UW, a cancelled registration (https://openairdocs.org/deregistered/N113UW-2019-09-04) (OpenAirDocs)
- Registry model: Airbus Industrie A320-214 (registry code 3930316, https://openairdocs.org/model/airbus-industrie-a320-214) (OpenAirDocs)
- Registry engine: CFM International CFM56 series (registry code 13802, https://openairdocs.org/engine/cfm-international-cfm56-series) (OpenAirDocs)
- Reported make and model: AIRBUS INDUSTRIE A320-214
- Reported engine: CFM INTL. CFM56 SERIES
- People aboard: 154
- Fatal injuries: 0
- Other injuries: 2
- Pilot certificates: Airline transport
- Pilot flight hours: 23,830 total, 4,457 in this make and model, 159 in the last 90 days
- NTSB investigation: [NTSB DCA14MA081](https://openairdocs.org/ntsb/DCA14MA081) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140313003339A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AS THE CREW TAXIED ONTO THE RUNWAY FOR DEPARTURE THE CAPTAIN NOTICED THAT THE WRONG DEPARTURE RUNWAY (27R) WAS DISPLAYED ON HIS NAVIGATION DISPLAY (ND). THE FIRST OFFICER (FO) CORRECTED THIS BY ENTERING RUNWAY 27L INTO THE MULTIFUNCTION CONTROL DISPLAY UNIT (MCDU).  CHANGING THE RUNWAY IN THE MCDU REQUIRES THE CREW TO MANUALLY RE-VERIFY THE ?V? SPEEDS AND FLEX TEMPERATURE IN THE MCDU.  THE CREW FAILED TO ACCOMPLISH THIS STEP AND SO THE AIRCRAFT HAD NO DATA AVAILABLE TO COMPUTE AND PERFORM A FLEX TAKEOFF OR DISPLAY SPEEDS ON THE PFD?S.  AS A RESULT, WHEN THE CAPTAIN ADVANCED THE THROTTLES A CHIME WAS HEARD FOLLOWED BY THE WARNING MESSAGE: ENG THR LEVERS NOT SET; SET TOGA; DISPLAYED ON THE UPPER ELECTRONIC CENTRALIZED AIRCRAFT MONITORING (ECAM) DISPLAY SCREEN.  THE CAPTAIN ASKED THE FO WHAT THE CHIME WAS; THE FO REPLIED ?POWER NOT SET? BUT FAILED TO READ THE ENTIRE MESSAGE, WHICH INSTRUCTED THE FLIGHT CREW TO SET THE THROTTLE TO THE TAKE-OFF GO AROUND (TOGA) SETTING.  THE CAPTAIN REPLIED TO THE FO WITH :THE POWER IS SET? AND ALSO STATED THAT HE ONLY ADVANCED THE THROTTLE JUST PAST THE FLEXIBLE TAKE-OFF (FLEX) THROTTLE POSITION, THEN BACK TO THE FLEX POSITION. ONCE THE AIRCRAFT REACHED 80 KNOTS A CONTINUOUS ?RETARD RETARD RETARD?, (THIS MESSAGE INSTRUCTS THE FLIGHT CREW TO MOVE THE THROTTLE TO THE IDLE POSITION DURING LANDING) AURAL WARNING MESSAGE WAS SOUNDED.  THE CAPTAIN STATED ?WE?LL GET THAT STRAIGHT WHEN WE GET AIRBORNE?.

AIRCRAFT LIFTED OFF, CLIMBED TO APPROXIMATELY SEVENTY FEET.  THE CAPTAIN STATED THAT ONCE THE WHEELS WERE OFF THE GROUND, HE HAD THE PERCEPTION THAT THE AIRCRAFT WAS UNSAFE TO FLY AND MOVED THE THROTTLES TO THE IDLE POSITION.  AIRCRAFT CONTACTED THE RUNWAY, THE TAIL SECTION OF THE AIRCRAFT STUCK THE RUNWAY, FOLLOWED BY THE MLG, DRIVING THE NOSE LANDING GEAR INTO THE RUNWAY CAUSING THE NLG TIRE?S TO BLOW AND THE NLG TO COLLAPSE.  AIRCRAFT SLID APPROXIMATELY 2000? FEET AND CAME TO REST ADJACENT TO TAXIWAY S10 ALONG THE LEFT RUNWAY EDGE.  LEFT ENGINE INGESTED RUNWAY EDGE LIGHTS AND DIRT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DCA14MA081](https://openairdocs.org/ntsb/DCA14MA081), Mar 13, 2014: Airbus A320 - 214 (N113UW), Philadelphia, PA, substantial damage. Probable cause: the captain's decision to reject the takeoff after the airplane had rotated. Contributing to the accident was the flight crew's failure to follow standard operating procedures by not verifying that…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.