NTSB CAROL · Event
Event CHI98IA164
Registry · N675UP
FAA Aircraft Registry record.
Make / Model
BEECH 400A
Seats / Engines
10 seats · 2 engines
ADS-B equipped
Yes — Mode-S A8F01B
Registrant of record
WHEELS UP PARTNERS LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the open shielding on the #2 VHF transceiver coax connector which resulted in electromagnetic interference with the yaw damper system.
Factual narrative
On May 18, 1998, at 0215 central daylight time, a Boeing 747-123, N675UP, operated by United Parcel Service (UPS) experienced uncommanded yaw damper inputs during cruise flight at FL350 while en route to Anchorage Alaska. The flight diverted to Minneapolis, Minnesota, where an uneventful landing was made. The captain, first officer, and flight engineer were not injured and the airplane was not damaged. The 14 CFR Part 121 cargo flight was operating on an IFR flight plan. The flight originated from Louisville, Kentucky, at 0159 eastern daylight time. While en route, the flight crew received an intermittent fire warning light and bell which they suspected was from the lower cargo area. They contacted UPS Maintenance Control using the VHF #2 transceiver and were unable to isolate the warning so they initiated a diversion to Minneapolis. While communicating with Maintenance Control the flight crew experienced several uncommanded "kicks" of the yaw damper. According to UPS, the flight crew turned off the upper yaw damper, but they did not turn off the lower yaw damper. They continued to experience "kicks" although not as severe. The flight landed at Minneapolis without incident at 0320 cdt. The crew write-up in the maintenance logbook regarding the uncommanded yaw damper "kicks" stated "Experienced rapid severe uncommanded flt control inputs in crz flt and then after with autopilots A or B or autopilot off, air divert to MSP." The crew reported during a debrief that the "kicks" occurred with either the "A" or "B" autopilots engaged. They reported turning the autopilot off at approximately FL150. A review of the Flight Data Recorder data indicated that approximately 45 minutes into the flight the #2 VHF was keyed at which time the upper rudder surface deflected left to a maximum of 3.3 degrees and the lower rudder surface deflected left to a maximum of 1.1 degrees. The data also shows that in addition to the yaw damper inputs, uncommanded movement of the control wheel occurred whenever the #2 VHF was keyed. The maximum control wheel movement was 16.9 degrees to the right. The control wheel deflections continued to occur after the upper yaw damper was disconnected as long as the autopilot was engaged. Maintenance inspection of the airplane after the incident revealed an open shield at the #2 VHF coax connector. The #2 VHF transceiver is located near the yaw damper couplers, and the pitch and roll computers. The connector was replaced and the airplane was returned to service. Inspection of the airplane did not reveal any evidence of a fire. The intermittent fire warning was corrected by maintenance personnel replacing the fire warning circuit card. On May 17, the day previous to this incident, a different flight crew who flew N675UP reported "When keying mic on #2 VHF (all three mics) Yaw Damper Kicks! Pulled #2 VHF CB [circuit breaker]." Maintenance inspection of the airplane after this event determined the #2 transceiver was unserviceable and it was replaced. Operational checks of the transceiver and yaw damper were conducted and the airplane was put back in service. While troubleshooting a fire warning indication with company maintenance control using the #2 VHF transceiver, the crew experienced several uncommanded 'kicks' of the yaw damper. The crew turned off the upper yaw damper, but not the lower. They continued to experience 'kicks' although not as severe. The flight departed to Minneapolis where it landed uneventfully. Inspection of the airplane after the incident revealed an open shield at the #2 VHF coax connector which is located near the yaw damper control box. The connector was replaced and the airplane was returned to service. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_CHI98IA164.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- NASA NTRS 2024 · Technical Memorandum (TM)
Testing of Advanced Capabilities to Enable In-time Safety Management and Assurance for Future Flight Operations
In order to refine an initial Concept of Operations, explore Concepts of Use, and expose/validate requirements for future In-Time Aviation Safety Management Systems (IASMS), testing architectures were…
- arXiv 2024 · arXiv preprint
A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
Browse the full corpus — academia portal ↗