FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX93FA033 · Sabreliner Corp. N-265-60

7 Nov 1992 · Phoenix, AZ, United States

Sabreliner Corp. N-265-60 · Accident: airframe, component or system failure during landing

From Salina Municipal Airport (SLN) to an unrecorded destination

Report a problem

Event

NTSB case
LAX93FA033
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Sabreliner Corp. N-265-60

Aircraft type
Sabreliner N-265
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
N169RF
Operator
Price, Halford · private individual
Onboard fatalities
Unknown
Route
From Salina Municipal Airport (SLN), Salina, KSTo 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 91: General Aviation
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
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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Brakes(normal), delayed
  • Pilot in command › Emergency procedure, not performed

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

NTSB narrative

UPON LANDING AT THE COMPLETION OF A CROSS COUNTRY FLIGHT, THE CAPTAIN OF THE TURBOJET AIRCRAFT EMPLOYED AERODYNAMIC BRAKING AND THRUST REVERSE TO SLOW THE AIRPLANE TO ABOUT 60 KNOTS. THE CAPTAIN WAS ALLOWING THE AIRPLANE TO ROLL TOWARD THE END OF THE RUNWAY WHERE THE OWNER/CO-PILOT'S HANGER WAS LOCATED. WITH ABOUT 4,000 FEET OF RUNWAY REMAINING, THE CAPTAIN APPLIED THE BRAKES. NO BRAKING ACTION WAS NOTED. THE AIRPLANE CONTINUED OFF THE END OF THE RUNWAY, THROUGH A FENCE AND BLOCK WALL INTO A PARKING LOT WHERE THE LEFT WING OF THE AIRPLANE WAS SEVERED. A POST CRASH FIRE CONSUMED ABOUT HALF OF THE AIRPLANE. EMERGENCY BRAKING PROCEDURES WERE NOT EMPLOYED. THE CREW REPORTED THAT THE WERE UNABLE TO SHUT DOWN THE ENGINES. THE CO-PILOT LACKED EXPERIENCE IN THE AIRCRAFT AND CREW COORDINATION DURING THE APPROACH, LANDING, AND EMERGENCY WAS INEFFECTIVE. THE AIRPLANE TRAVELED ABOUT 11,000 FEET FROM POINT OF TOUCHDOWN TO POINT OF REST. EXAMINATION OF THE BRAKING AND HYDRAULIC SYSTEMS FAILED TO PINPOINT A MALFUNCTION.

Probable cause

THE DELAY OF THE PIC TO APPLY NORMAL BRAKING AND HIS FAILURE TO EXECUTE THE APPROPRIATE EMERGENCY PROCEDURES. CONTRIBUTING TO THIS ACCIDENT WAS AN UNDETERMINED ANTISKID MALFUNCTION; THE COPILOT'S INEXPERIENCE IN THE AIRCRAFT; AND INADEQUATE CREW COORDINATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX93FA033
Event ID
20001211X16048
Case number
LAX93FA033
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 1992-11-08.
  • API snapshot SHA-256: c6efc887850fd136a25b8610e1ea78c2ebc071f6a5a8b5c74593a790336cac6c; retrieved 2026-09-23T02:29:34.927Z.