FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC84FA114 · Canadair CL-600 CHALLENGER CL-600 CHA

2 Apr 1984 · Little Rock, AR, United States

Canadair CL-600 CHALLENGER CL-600 CHA · Accident: loss of control on ground/water during landing

Report a problem

Event

NTSB case
MKC84FA114
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

Canadair CL-600 CHALLENGER CL-600 CHA

Aircraft type
Canadair CL-600
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
N800CC
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
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 › Supervision, inadequate

Approximate · Estimated position: the centre of Little Rock, AR, the place the record names. Not the accident site.

NTSB narrative

THE ACFT WAS ON AN FAA CERTIFICATION FLT (EXPERIMENTAL). DURING THE RECOVERY PHASE, A NON-TYPE RATED FAA PLT WAS IN THE L SEAT & THE PIC WAS IN THE R SEAT. WHILE DESCENDING, A DUCT FAIL LGT & A LEADING EDGE OVERHEAT LGT CAME ON. THE PIC TOOK CORRECTIVE ACTION. THE FAA PLT MADE AN ILS APCH TO RWY 22 WHICH WAS WET. THE APCH WAS MADE WITH THE L ENG AT HI IDLE. THE THRUST REVERSERS WERE NOT ARMED FOR THE LANDING. A TOUCHDOWN WAS MADE ABOUT 2000' DOWN THE RWY & SPOILERS WEREDEPLOYED. WHEN THE FAA PLT REALIZED HE DID NOT HAVE REVERSE THRUST, HE TRIED SLOWING THE ACFT WITH BRAKES; HOWEVER, THE L BRAKE WAS INOP. THE PIC TOOK CONTROL & CYCLED THE ANTI-SKID, BUT STILL HAD NO L BRAKING ACTION. SUBSEQUENTLY, THE ACFTRAN OFF THE END OF THE RWY & THE NOSE GEAR COLLAPSED IN MUDDY TERRAIN. AN INVESTIGATION REVEALED THAT DURING MAINTEN- ANCE, THE SPEED SENSOR HARNESSES FOR THE L MAIN GEAR WERE REVERSED WHICH ELIMINATED ANY BRAKING TO THE L BRAKE WHILE THE ANTI-SKID WAS ON.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC84FA114
Event ID
20001214X39359
Case number
MKC84FA114
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: 0ca444096df9e1d4acfd7b974fd5b0406e639ab0adb906d4738fdb0f2dc94878; retrieved 2026-09-23T20:40:17.676Z.