DCA82IA021 · Gates Learjet 24B
Delaware Victor Air Service Gates Learjet 24B · Incident: airframe, component or system failure en route
From AI · PBI to AI · IAH
Event
- NTSB case
- DCA82IA021
- 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
- Incident
- 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
Gates Learjet 24B
- 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
- N721J
- Operator
- Delaware Victor Air Service
- Onboard fatalities
- Unknown
- Route
- From AI · PBITo AI · IAH
- 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
- En route · climb to cruise
- 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
- None
Cause areas
- Pilot in command › Autopilot, not understood
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
WHILE CLIMBING TO A CRUISE ALTITUDE OF 41000 FEET, THE PILOT ENGAGED THE AUTOPILOT AT APPROXIMATELY 29500 FEET. THE AIRCRAFT STARTED TO PITCH NOSE DOWN SEVERAL SECONDS LATER. THE PITCH TRIM SWITCH WAS TURNED OFF AND THE CIRCUIT BREAKERS PULLED. THE PILOTS WERE AIDED BY A PASSENGER AND USED ALL THEIR STRENGTH TO PULL BACK ON THE CONTROL WHEEL TO KEEP THE AIRCRAFT FROM CONTINUING TO PITCH NOSEDOWN. THE AIRCRAFT LANDED SAFELY. EXAMINATION OF AUTO- PILOT REVEALED THAT AN OVERVOLTAGE CONDITION EXISTED THAT WAS DRIVING THE STAB TRIM ACTUATOR TO THE AIRPLANE NOSE DOWN POSITION. IN ADDITION, THIS CAUSED THE AUTOPILOT EFFORT INDICATOR TO SHOW A MAXIMUM NOSE DOWN DEFLECTION. ACCORDING TO THE COPILOT'S STATEMENT, THE EFFORT INDICATOR WAS AT MAXIMUM DEFLECTION DURING THE PRE-TAKEOFF CHECK.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DCA82IA021
- Event ID
- 20020917X03106
- Case number
- DCA82IA021
- 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, damage. 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: b8a703d42b9103c5d3f4c9a83d6c18b1607309acc7a1d2b12950e27fd736a385; retrieved 2026-09-24T03:15:52.380Z.