FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 179 · Boeing 747-236

27 Feb 2000 · Providence, RI, United States

Boeing 747-236 · Accident: airframe, component or system failure en route

From London Heathrow Airport (LHR) to John F. Kennedy International Airport (JFK)

Report a problem

Event

NTSB case
NYC00LA085
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
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Boeing 747-236

Aircraft type
Boeing 747
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
GBDXL
Operator
Unknown
Onboard fatalities
Unknown
Route
From London Heathrow Airport (LHR), LondonTo John F. Kennedy International Airport (JFK), Jamaica, NY
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 129: Foreign
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 · descent
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

  • Company maintenance personnel › Maintenance, improper

Approximate · Estimated position: the centre of Providence, RI, the place the record names. Not the accident site.

NTSB narrative

The airplane was in cruise flight when it began a descent from flight level 350. At the same time, the flight engineer was reconfiguring the airplane's electrical system from a Category III landing to a Category I landing. When the flight engineer closed the "number one bus-tie-breaker," the airplane experienced an uncommanded pitch-up, accompanied by numerous momentary instrument failures. Twelve occupants were injured. The airplane was utilizing the "A" autopilot system, which remained engaged. The pilot disconnected the autopilot, leveled the airplane, re-engaged the autopilot, and continued to an uneventful landing. During a ferry flight, maintenance personnel were able to duplicate a "sudden pitch-up" while using the airplane's "B" autopilot system, and closing the "number two bus-tie-breaker." Additionally, the flight crew reported that the airplane "felt light in pitch." Examination of data obtained from the flight data recorder and optical quick access recorder revealed an electrical discontinuity around the time of the pitch-up. An inspection of the airplane revealed that the number 1 and 2, elevator feel computer pitot connections were capped. Review of the airplane's maintenance history revealed that the airplane had recently undergone an "inter 2 check" at a British Airways maintenance facility. During that time, maintenance personnel disconnected the pitot connections to the elevator feel computer in order to perform pitot static system checks. The effect of the disconnected pitot-static lines on the elevator feel computer would have resulted in a more extreme travel of the elevator control surface. The calculated expected autopilot elevator authority for the accident flight was about 4 degrees. The estimated actual elevator deflection during the accident sequence was 6.87 degrees nose up, and 6.97 degrees nose down. Review of the Boeing basic airplane maintenance manual section that detailed the pitot-static system checks revealed a test to confirm that the elevator feel computer was reconnected and functioned. The test was not present the maintenance manual utilized by British Airways, which was provided by Boeing. The source of the pitch-up command to the autopilot was not determined; however, when the autopilot system was properly configured, the pitch-up characteristics were not objectionable and within expected values.

Probable cause

Maintenance personnel's failure to reconnect the pitot connections to the elevator feel computer which resulted in an elevator control surface deflection which was outside of the normal autopilot elevator authority. The uncommanded autopilot input to the elevator control surface resulted from an undetermined electrical source. A factor in this accident was that the section of the 747 Maintenance Manuel utilized by company maintenance personnel did not contain an "elevator feel light test."

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC00LA085
Event ID
20001212X20563
Case number
NYC00LA085
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: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-02-28.
  • API snapshot SHA-256: 7c1d9f18db9ec3b7c8d82ad336870b432ab3de2458e29d2b636dfec3a3315456; retrieved 2026-09-18T16:47:49.713Z.