US Airways Flight 1702

From EverybodyWiki Bios & Wiki
US Airways Flight 1702
N113UW (6993382739).jpg
N113UW, the aircraft involved, two years before the accident.
DateMarch 13, 2014 (2014-03-13)
SummaryPilot error
SitePhiladelphia International Airport, Philadelphia, Pennsylvania, United States
39°51′45″N 75°15′51″W / 39.86250°N 75.26417°W / 39.86250; -75.26417Coordinates: 39°51′45″N 75°15′51″W / 39.86250°N 75.26417°W / 39.86250; -75.26417
Fatal error: The format of the coordinate could not be determined. Parsing failed.

Aircraft typeAirbus A320-200
OperatorUS Airways
Flight originPhiladelphia International Airport
DestinationFort Lauderdale–Hollywood International Airport

US Airways Flight 1702 (US1702/AWE1702) was a scheduled domestic passenger flight which was involved in an aircraft accident which occurred during take-off from Philadelphia International Airport on March 13, 2014. The Airbus A320-200 operated by US Airways had 154 people on board: 149 passengers and 5 crew members.[1][2]

After a lengthy investigation the National Transportation Safety Board released its findings that pilot error contributed to the accident. The accident report stated the captain's conducting an abnormal takeoff and his decision to abort the takeoff after the aircraft had already become airborne caused the accident. As of late 2017 neither the captain nor first officer had been re-instated to flight status by the airline (now American Airlines following a merger).[3][4][5][6]


The aircraft involved, registered N113UW (MSN 1141), was an Airbus A320-200 that first flew on November 22, 1999 and was delivered new to US Airways. The aircraft had accumulated 19,932 cycles as of the end of December 2013.[7][8]


Before pushback from the gate, the first officer, who was the pilot monitoring, initialized the flight management system (FMS) and mistakenly entered the incorrect departure runway 27R instead of the assigned 27L. As the captain taxied the aircraft to runway 27L he noticed the incorrect input and asked the first officer to correct the error, which she did. However the first officer did not enter the FLEX temperature or the related V speeds for the newly entered runway.[9] As a result, the FMS' ability to execute a FLEX power takeoff was invalidated, and V speeds did not appear on the primary flight displays (PFDs) or the multipurpose control display unit during the takeoff roll.

Once the aircraft was cleared for takeoff the captain set FLEX power and did not notice any abnormalities. Once the aircraft reached 56 knots indicated airspeed the flight crew received a single level-two caution chime and an electronic centralised aircraft monitor (ECAM) message indicating that the engines' thrust was not set correctly. The first officer called "engine thrust levers not set". The captain responded "they're set".[10]

As the aircraft continued to accelerate, the first officer did not make a call out at 80 knots, as required. As the aircraft reached 86 knots the automated "RETARD" aural alert sounded. The captain later said he did not hear the alert. The aircraft rotated at 164 knots and suffered a tailstrike; the aircraft climbed to between 20–30 feet in altitude then the captain entered the aircraft in a nose down attitude, then immediately afterward achieved a 6.7 degree nose-high attitude. The aircraft descended until the nose gear and right main gear impacted the runway, causing the aircraft to bounce 15 feet back into the air before descending rapidly. The aircraft touched down heavily on its nose landing gear first which caused the front gear to collapse. The aircraft then slid down the runway and came to rest off to the left side. The crew then evacuated the cabin immediately as a small oil fire broke out in the left engine, which was quickly extinguished by fire crews.[11][12]



National Transportation Safety Board (NTSB) and Federal Aviation Administration (FAA) crews were on scene within hours. The aircraft remained at its resting place for 14 hours while the scene was photographed and investigators started the aircraft inspection. The aircraft was then towed to a hangar where it remained for most of the investigation. Early reports from the airline and media were that the nose landing gear collapsed, causing the aircraft to skid down the runway. However upon interviewing the flight crew and analyzing data from the flight recorders, the NTSB determined that the aircraft had rotated, climbed and descended until it hit the runway. In the final NTSB report it was stated, once the "RETARD" alert was heard, the aircraft was unable and unsafe to fly and the takeoff should have been aborted.[13][14]

The NTSB stated the cause to be pilot error.[15][16]

Airline response[edit]

US Airways initially said that the accident was caused by a blown tire.[17] The airline stood behind this claim until the FAA released a video showing the aircraft leaving the ground then impacting the runway nose first and the nose landing gear collapsing. In a statement following the release of the investigation findings US Airways said it would increase the training of its pilots on how to abort and what to do once airborne. As of 2017 the airline had not brought back the pilots involved in the incident.[7]

See also[edit]

  • FedEx Express Flight 910
  • Southwest Airlines Flight 345
  • United Airlines Flight 173
  • List of accidents and incidents involving the Airbus A320 family
  • List of accidents and incidents involving commercial aircraft
  • List of accidents and incidents involving airliners in the United States


  1. "US Airways crash last year likely due to pilot error". Retrieved 2018-07-26.
  2. "A US Airways Plane Skidded Off the Runway in Philly". Retrieved 2018-07-26.
  3. "NTSB: Pilot mistakes caused US Airways accident in Philadelphia". USA TODAY. Retrieved 2018-07-26.
  4. "Pilots played role in US Airways 1702 crash: FAA". 2014-12-12. Retrieved 2018-07-26.
  6. "Pilot Error Blamed for 2014 Botched US Airways Takeoff". ABC News. 2016-02-26. Retrieved 2018-07-26.
  7. 7.0 7.1 "US Airways Airbus A320 Off Runway in Philadelphia & The Power of Social Media". AirlineReporter. 2014-03-13. Retrieved 2018-07-26.
  8. "U.S. Airways Plane Malfunctions on Takeoff at Philadelphia Airport". Time. Retrieved 2018-07-26.
  9. "NTSB: Pilot error led to aborted takeoff in Philadelphia". Retrieved 2018-07-26.
  10. "8 lessons we can learn from the aborted flight of US Airways flight 1702 - Travelers United". Travelers United. 2014-03-17. Retrieved 2018-07-26.
  11. "ASN Aircraft accident Airbus A320-214 N113UW Philadelphia International Airport, PA (PHL)". Retrieved 2018-07-26.
  12. "US Airways Flight 1702: What passengers say happened". Christian Science Monitor. 2014-03-15. ISSN 0882-7729. Retrieved 2018-07-26.
  13. "Report: Pilots in Philly Crash Ignored Warnings". NBC 10 Philadelphia. Retrieved 2018-07-26.
  14. "Passenger narrates her evacuation from US Airways Flight 1702". Mail Online. Retrieved 2018-07-26.
  15. "NTSB cites pilot error in March 2014 aborted takeoff and nose gear collapse at PHL". Retrieved 2018-07-26.
  16. "USAirways 1702 - Philadelphia International Airport Philadelphia, PA – March 13, 2014". Retrieved 2018-07-26.
  17. Remizowski, Leigh; Ferrigno, Lorenzo; Botelho, Greg. "US Airways plane blows tire on takeoff in Philadelphia, comes to stop". CNN. Retrieved 2018-07-26.

External links[edit]

This article "US Airways Flight 1702" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:US Airways Flight 1702. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.