Peruvian Airlines Flight 112
Boeing 737-3M8 · Landing gear collapse after a hard landing caused by mechanical failure
From Jorge Chávez International Airport (LIM) to Francisco Carle Airport (JAU)
Event
- NTSB case
- DCA17RA082
- 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
- Unknown · led by another country; figures from NTSB notifications
- Event fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 150
- Survivors
- 150
- 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
- 39
- 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
- Not recorded
Boeing 737-3M8
- Flight
- P9112
- Aircraft type
- Boeing 737
- 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
- OB-2036-P
- Operator
- Peruvian Airlines
- Onboard fatalities
- 0
- Route
- From Jorge Chávez International Airport (LIM)To Francisco Carle Airport (JAU)
- 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
- Not recorded
- 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
- Landing · landing roll
- 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
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Estimated position: Francisco Carle Airport, the airport the Wikipedia article names as the site. Where on or near it is not known.
From the Wikipedia article
Peruvian Airlines Flight 112 was a domestic scheduled passenger flight operated by a Boeing 737-300 from Lima to Jauja in Peru. On 28 March 2017, the aircraft operating the flight suffered undercarriage collapse after landing, caught fire, and was burnt out. While no fatalities occurred in this accident, 39 of the 150 people on board were injured.
Accident
The aircraft landed at Jauja at 16:40 local time (21:40 UTC). Passengers reported "two strong impacts" on landing. All three landing gear legs collapsed and the aircraft slid along the runway and departed the runway to the right, and the starboard wing hit the airport's perimeter fence. A fire broke out and destroyed the aircraft. All 141 passengers and nine crew on board escaped, of whom 39 people were injured and taken to hospital. Two people sustained broken bones, and three people sustained concussions. The accident was captured by several passengers on board.
Text from the Wikipedia article “Peruvian Airlines Flight 112” (revision 1365836477, 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 government of Peru has notified the NTSB of an accident involving a BOEING 737 that occurred on March 28, 2017. The NTSB has appointed a U.S. Accredited Representative to assist the government of Peru's investigation under the provisions of ICAO Annex 13 as the State of Manufacturer and Design of the airplane.All investigative information will be released by the government of Peru.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
Wikipedia article: Peruvian Airlines Flight 112
- Article
- Peruvian Airlines Flight 112
- Revision
- 1365836477 · 2026-07-24 · retrieved 2026-09-18
- Wikidata
- Q30632824
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA17RA082
- Event ID
- 20170328X25518
- Case number
- DCA17RA082
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Peruvian Airlines Flight 112" (page 53628166, revision 1365836477); merged with NTSB case DCA17RA082 (events / aircraft)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: airport the Wikipedia infobox site links (Wikidata code, OurAirports)
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA17RA082
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "Peruvian Airlines Flight 112" and NTSB case DCA17RA082, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- No bulk values were replaced by the NTSB case API.