NYC01IA199 · Raytheon 400A
Raytheon 400A · Incident: airframe, component or system failure on approach
From Dillant Hopkins Airport (EEN) to Teterboro Airport (TEB)
Event
- NTSB case
- NYC01IA199
- 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
- Unknown
- 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
Raytheon 400A
- Aircraft type
- Raytheon 400
- 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
- N3337J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dillant Hopkins Airport (EEN), Keene, NHTo Teterboro Airport (TEB), Teterboro, NJ
- 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
- 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
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was approximately 10 miles west of the airport at 4,000 feet msl, and indicating 220 knots of airspeed, when the captain felt an abnormal yaw input. At first, he thought the yaw dampener had failed. He selected the dampener to "OFF," but did not regain normal rudder control. The captained continued the approach, and landed uneventfully. An inspection by maintenance personnel revealed that the right aft rudder cable had separated. The cable was change 50.6 hours before the incident. The incident rudder cable met its original design specifications, and had separated in overload created by a bend or kink in the cable. Examination of the cable guide revealed a shiny wear pattern with no scrapes or gouges. The break in the rudder cable was within 1 inch of the aft cable guide for the right aft rudder pulley. Two separate incidents involving flight control cables being improperly installed over a cable guide were examined. In both cases, the cables separated, but the cable guides remained intact. The wear patterns on the cable guides for the previous incidents were similar to that of the incident cable guide.
Probable cause
The right aft rudder cable being installed over a cable guide by maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01IA199
- Event ID
- 20010817X01722
- Case number
- NYC01IA199
- 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: a70d33924c5a51cb19dbcf70e1322e1c755b5af110eaca525070c2172dab3153; retrieved 2026-09-22T11:45:20.433Z.