FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ENG10RA020 · BAE 146 300

9 Mar 2010 · Jorge Chavez Intl Airport, Peru Narrative disagrees

BAE 146 300 · Incident

From Jorge Chávez International Airport (SPIM) to Lima

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ENG10RA020
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
Incident
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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
Unknown
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

BAE 146 300

Aircraft type
BAE 146
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-1914-P
Operator
Star Peru
Onboard fatalities
Unknown
Route
From Jorge Chávez International Airport (SPIM), Jorge Chavez Intl AirportTo Lima
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
Unknown
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
Not recorded
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
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

On March 9, 2010, a Star Peru British Aerospace BAe 146-300, registration OB-1914-P, powered by 4 Honeywell ALF502R engines, experienced a No. 1 engine uncontained failure during take off run on Runway 33 of the Jorge Chavez International Airport, Lima, Peru. The takeoff was aborted. There was minor airplane damage. No injuries were reported.

This incident is being investigated by Peru's Comision de Investigacion de Accidentes de Aviacion (CIAA). Further information about this incident can be obtained from:

Patrik Frykberg, Investigator In Charge Comision de Investigacion de Accidentes de Aviacion Ministerio de Transportes y Comunicaciones PERU

Tel: 51-1-6157488 Fax: 51-1-6157800 Anx 3030 Cel: 51-1-997881886 Nextel: 51-1-994235213 Id: 423*5213 Movistar: 51-1-988031027 RPM: #705246

This report is for informational purposes and contains only information obtained for or released by The Republic of Peru.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ENG10RA020
Event ID
20100319X00856
Case number
ENG10RA020
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.
  • No bulk values were replaced by the NTSB case API.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: f414fb057ed48b7896f87fe7da8daa7525bf82b5cc6fb4a884d36ddaaa9e490f; retrieved 2026-09-15T13:45:42.198Z.