FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

New Creations Learjet LR25B-XR accident

1 Jul 1991 · Columbus, OH, United States

Learjet LR25B-XR · Accident: loss of control on ground/water during landing

From Philadelphia International Airport (PHL) to an unrecorded destination

Report a problem

Event

NTSB case
NYC91LA163
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
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
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 LR25B-XR

Aircraft type
Learjet LR25
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
N458J
Onboard fatalities
Unknown
Route
From Philadelphia International Airport (PHL), Philadelphia, PATo not recorded
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 135: Air Taxi & Commuter
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
First occurrenceThe 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
Loss of control on ground/water
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Go-around, not performed
  • Pilot in command › Visual lookout, not maintained

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

NTSB narrative

N458J WAS LANDING DURING A RAIN SHOWER. AS THE AIRPLANE STARTED TO FLARE FOR LANDING, THE WIND CAUSED IT TO DRIFT TO THE RIGHT. THE PILOT STARTED TO CORRECT THIS DRIFT, AS THE RAIN BECAME HEAVIER. DURING THE TOUCHDOWN, THE PILOT LOST VISUAL REFERENCE WITH THE RUNWAY, YET HE CONTINUED WITH THE LANDING ROLL. THE AIRPLANE DRIFTED OFF THE LEFT SIDE OF THE RUNWAY AND RAN INTO SOFT TERRAIN.

Probable cause

THE FAILURE OF THE PILOT TO MAINTAIN VISUAL REFERENCE WITH THE RUNWAY DURING A LANDING, WHICH RESULTED IN A LOSS OF DIRECTIONAL CONTROL. ALSO CAUSAL TO THE ACCIDENT WAS THE PILOT'S FAILURE TO INITIATE A GO-AROUND, AFTER HE LOST SIGHT OF THE RUNWAY DURING THE TOUCHDOWN. FACTORS RELATED TO THE ACCIDENT WERE THE HEAVY RAIN AND THE LACK OF RUNWAY CENTERLINE LIGHTS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC91LA163
Event ID
20001212X17656
Case number
NYC91LA163
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1991-07-02.
  • API snapshot SHA-256: defff623c0f1bdd26ce07a5bf2206b3873d30db7036fd81e7345b8b6d8a4030f; retrieved 2026-09-18T18:54:14.590Z.