CHI90LA115 · Beech F33A
Delta Delta Partnership Beech F33A · Accident: abrupt maneuver on approach
From Hector International Airport (FAR) to an unrecorded destination
Event
- NTSB case
- CHI90LA115
- 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
Beech F33A
- Aircraft type
- Beechcraft 33
- 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
- N179DD
- Operator
- Delta Delta Partnership
- Onboard fatalities
- Unknown
- Route
- From Hector International Airport (FAR), Fargo, NDTo 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
- Approach · IFR initial approach
- 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
- Abrupt maneuver
- 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 › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT ENGAGED THE AUTOPILOT APPROACH MODE TO EXECUTE A COUPLED ILS APPROACH WHILE HE WAS HIGH AND FAST WITH A 2000 FOOT PER MINUTE RATE OF DESCENT. THIS WAS OUTSIDE THE PARAMETERS FOR A STABILIZED APPROACH. WHEN THE AUTOPILOT CAPTURED THE GLIDE SLOPE, THE AIRCRAFT NOSED OVER SHARPLY, FLEW THROUGH THE GLIDE SLOPE, PULLED UP SHARPLY, FLEW THROUGH THE GLIDE SLOPE GOING UP, AND NOSED OVER AGAIN BEFORE THE PILOT COULD DISENGAGE THE AUTOPILOT. PILOT LANDED THE AIRCRAFT WITHOUT FURTHER INCIDENT, BUT THE PITCH EXCURSIONS HAD EXCEEDED THE STRESS LIMITS OF THE AIRCRAFT.
Probable cause
THE UTILIZATION OF IMPROPER PROCEDURES ON THE PART OF THE PILOT IN COMMAND BY ATTEMPTING TO EXECUTE A COUPLED APPROACH OUTSIDE THE PARAMETERS OF THE AUTOPILOT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA115
- Event ID
- 20001212X22885
- Case number
- CHI90LA115
- 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: 76dcee0286c4b51934c2f6deaba7328f276fee5b994e1d7e596d4bd8e4cc79a3; retrieved 2026-09-21T23:54:59.795Z.