Connie Kalitta Services Learjet 23 accident
Learjet 23 · Accident: on ground/water collision with terrain/water during landing
From Youngstown Warren Regional Airport (YNG) to an unrecorded destination
Event
- NTSB case
- ATL91LA122
- 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
- Visual Meteorological Cond
Learjet 23
- Aircraft type
- Learjet 23
- 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
- N500FM
- Operator
- Connie Kalitta Services
- Onboard fatalities
- Unknown
- Route
- From Youngstown Warren Regional Airport (YNG), YOUNGTOWN, OHTo 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 · 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
- On ground/water collision with terrain/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 › Planning/decision, premature
- Pilot in command › Procedures/directives, discontinued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD COMPUTED LANDING PERFORMANCE INFORMATION FOR A LANDING ON A WET RUNWAY WITH ANTI-SKID; SUFFICIENT RUNWAY SURFACE WAS AVAILABLE. TOUCHDOWN WAS NORMAL, HOWEVER DURING THE BRAKING PROCESS, THE AIRPLANE STARTED TO FISHTAIL AND THE PILOT BELIEVED THAT THE ANTI-SKID SYSTEM HAD FAILED. THEREFORE, THE PILOT TURNED THE ANTI-SKID SYSTEM OFF AND CONTINUED THE ROLLOUT WITH NORMAL BRAKING. THE AIRPLANE WENT OFF THE DEPARTURE END OF RUNWAY 05 AND SUSTAINED SUBSTANTIAL DAMAGE. PERFORMANCE DATA INDICATED MORE RUNWAY SURFACE WAS REQUIRED FOR A SAFE LANDING ON A WET RUNWAY WITHOUT ANTI-SKID ASSISTANCE. THE BRAKING SEQUENCE OF EVENTS DESCRIBED BY THE PILOT RESEMBLED DYNAMIC HYDROPLANING WHERE THERE WAS A COMPLETE LOSS OF BRAKING EFFECTIVENESS RATHER THAN AN ANTI-SKID MALFUNCTION. AN EXAMINATION OF THE AIRPLANE FAILED TO DISCLOSE ANY MECHANICAL PROBLEMS.
Probable cause
THE PILOT'S PREMATURE DECISION TO TURN OFF THE ANTI-SKID DURING LANDING ROLL. FACTORS TO THIS ACCIDENT WERE HYDROPLANING CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91LA122
- Event ID
- 20001212X17433
- Case number
- ATL91LA122
- 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: 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: 1cb3cdb717a022fe2c22f0cb436279a64d734a25aad8e4402e06051bb7a1a7c6; retrieved 2026-09-18T18:54:08.246Z.