Boeing 757-200 TF-FII
20 October 2002 · Baltimore, Maryland, United States · No injuries
Summary
On 20 October 2002 at about 00:30 local time, a Boeing 757-200 registered TF-FII, operated by Icelandair - Fkygkeudur HF, was involved in an incident near Baltimore, Maryland, United States. 196 people were on board and nobody was injured. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:30
- Classification
- Incident
- Location
- Baltimore, Maryland, United States
- Coordinates
- 39.2898, -76.6196
- Aircraft
- Boeing 757-200
- Registration
- TF-FII
- Category
- Airplane
- Engines
- 2
- Operator
- Icelandair - Fkygkeudur HF
- Operating rule
- Part 129: Foreign
- Phase of flight
- Not recorded
- Route
- Orlando → Keflavik
- Aircraft damage
- Not recorded
- Light
- Night
- NTSB number
- DCA03IA005
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 196 | 0 | 0 | 0 | 196 |
Probable cause
The captain's improper procedures regarding stall avoidance and recovery. Contributing to the incident were the partial blockage of the pitot static system, and the flight crew's improper decisions regarding their use of inaccurate airspeed indications. Contributing to the flight crew's confusion during the flight were the indistinct alerts generated by the airplane's crew alerting system.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
During the takeoff roll as the captain was about to call "eighty" knots, the first officer called "hundred." The captain noted that the standby airspeed indicator agreed with the first officer's and decided to continue the takeoff and address the anomaly of his airspeed indicator after takeoff. The pilots indicated that EICAS messages appeared and disappeared several times after takeoff and during the climb, including the messages MACH/SPD TRIM and RUDDER RATIO. Checklists for MACH/SPD TRIM and RUDDER RATIO messages did not mention an unreliable airspeed as a possible condition. The modifications associated with Boeing Alert Service Bulletin 757-34A0222 (and mandated by FAA Airworthiness Directive 2004-10-15 after the incident), which had not been incorporated on the incident airplane, would have provided a more direct indication of the airspeed anomaly. According to information in the Icelandair Operations Manual, these EICAS messages (in conjunction with disagreements between the captain and first officer airspeed indicators) may indicate an unreliable airspeed. Overspeed indications and simultaneous overspeed and stall warnings (both of which occurred during the airplane's climb from FL330 to FL370) are also cited as further indications of a possible unreliable airspeed. The crew did take actions in an attempt to isolate the anomalies (such as switching from the center autopilot to the right autopilot at one point during the flight). However, this did not affect the flight management computer's use of data from the left (captain's) air data system, and the erroneous high airspeeds subsequently contributed to airplane-nose-up autopilot commands during and after the airplane's climb to FL370. During the climb the captain's indicated airspeed began to increase, and the overspeed warning occurred. The first officer indicated that at this time his airspeed indication and the standby airspeed indication both decreased to about 220 knots and his pitch attitude felt high. Despite agreement between the first officer and standby airspeed indications and the pilots' belief that the captain's airspeed indicator was inaccurate, control was transferred from the first officer to the captain. Pitch attitude continued to climb and airspeed continued to decay after the captain assumed control. The airplane's pitch attitude became excessively high until the airplane's stick shaker activated and the airplane stalled. Although stall recovery was eventually effected and the airplane was leveled at FL300, the lack of appropriate thrust and control column inputs following the stall delayed the recovery. Evidence from the investigation indicates that anomalies of the captain's airspeed indicator were caused by a partial and intermittent blockage of the captain's pitot tube. The reason for the blockage was not determined.
Quoted verbatim from the NTSB record.
Other Boeing 757 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 11 May 2002 | Boeing 757-33N | Chicago, Illinois, United States | American Trans Air | No injuries | - |
| 1 Jul 2002 | Boeing 757-23F | Uberlingen, Germany | DHL Airways Inc | Fatal | 71 |
| 29 May 2002 | Boeing 757-200 | Atlanta, Georgia, United States | Delta Air Lines Inc | Serious injuries | - |
| 10 Sep 2002 | Boeing 757-251 | Baltimore, Maryland, United States | - | No injuries | - |
| 2 Mar 2002 | Boeing 757-200 | Seattle, Washington, United States | - | No injuries | - |
| 18 Apr 2002 | Boeing 757-200 | Springfield, Missouri, United States | - | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 May 2002 | Beechcraft 400A | Baltimore, Maryland, United States | Flight Options, Inc. | No injuries | - |
| 19 May 2002 | Ayres S-2R | Swanton, Maryland, United States | - | Fatal | 1 |
| 20 Jun 2002 | Mooney M20 | Hagerstown, Maryland, United States | - | Serious injuries | - |
| 26 Jul 2002 | Beechcraft S-35 | Clear Spring, Maryland, United States | - | Fatal | 1 |
| 18 Dec 2002 | Bell 206B | Odenton, Maryland, United States | Glenwood Aviation LLC | No injuries | - |
| 1 Aug 2002 | Cessna 172K | Patuxent River, Maryland, United States | Patuxent River Naval Flying Club | Serious injuries | - |