Connie Kalitta Services Learjet 24 accident
Learjet 24 · Accident: on ground/water collision with object while taxiing
From Rick Husband Amarillo International Airport (AMA) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL90LA026
- 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 24 Possible conflict
- Aircraft type
- Learjet 24
- 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
- N500P
- Operator
- Connie Kalitta Services
- Onboard fatalities
- Unknown
- Route
- From Rick Husband Amarillo International Airport (AMA), Amarillo, TXTo 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
- Taxi · from runway
- 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 object
- 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 › Clearance, misjudged
- Pilot in command › Proper assistance, not used
- Pilot in command › Visual lookout, not maintained
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
WHILE TAXING ONTO RAMP AFTER LANDING AND PREPARING TO MAKE A 180 DEGREE TURN TO PARK BETWEEN TWO PARKED AIRCRAFT, THE PILOT MISJUDGED THE HEIGHT OF HIS AIRPLANE'S TAIL AS HE TAXIED UNDER THE WING OF A PARKED AIRPLANE. THE TAIL COLLIDED WITH THE WING OF THE PARKED AIRPLANE.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO INSURE HIS AIRPLANE WAS CLEAR OF A PARKED AIRCRAFT WHILE MANEUVERING TO PARK.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90LA026
- Event ID
- 20001213X29739
- Case number
- ATL90LA026
- 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: 85fd3273504d394b94fe84a366b200b573f282b98e07e4c96cc6bd0d0a704886; retrieved 2026-09-18T19:06:55.907Z.