FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Personas y Paquetes Por Aire S A de C V Learjet 25 D accident

4 Mar 2011 · Houston, TX, United States

Learjet 25 D · Accident: landing area overshoot

From Angel Albino Corzo International Airport (MMTG) to William P. Hobby Airport (KHOU)

Report a problem

Event

NTSB case
CEN11LA223
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
Charter & commuter
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

Learjet 25 D

Aircraft type
Learjet 25
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
XA-TWH
Onboard fatalities
Unknown
Route
From Angel Albino Corzo International Airport (MMTG), Tuxla GutierrezTo William P. Hobby Airport (KHOU), Houston, TX
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 129: Foreign
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 · flare/touchdown
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
Landing area overshoot
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

During an instrument landing in night instrument meteorological conditions, the airplane exited the far end of the runway and struck the instrument landing system localizer antenna system. The pilot and the co-pilot both reported that, due to fog and low visibility, the pilot flared the airplane too high and landed too long on the runway. The pilot applied maximum braking and reverse thrust, but could not stop the airplane before exiting the runway. The reported weather was visibility of 3/4 mile in mist and an indefinite ceiling at 200 feet. The operator reported that there was no mechanical malfunction or failure of the airplane that would have precluded normal operation. Both pilots were likely influenced by the mission pressure to land because of medical considerations for a passenger on board.

Probable cause

The flying pilot's failure to attain the proper touchdown point in low-visibility conditions, which resulted in a runway overrun. Contributing to the accident was mission pressure to land at that airport.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA223
Event ID
20110312X24318
Case number
CEN11LA223
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. 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: 51e6b06086d95408cf8175735a4499d4983a4921468cda9a953d6e46dbfb9e54; retrieved 2026-09-15T15:54:09.445Z.