Crash of a De Havilland DHC-6 Twin Otter 200 in Washington-Dulles: 1 killed

Date & Time: Jul 20, 1988 at 1608 LT
Registration:
N7267
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Washington - Washington
MSN:
195
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
12400
Aircraft flight hours:
10513
Circumstances:
This was the first flight after a maintenance inspection. The flaps were left full down after a post-inspection by company mechanics, before the flight. Witnesses stated the flaps were down when the aircraft taxied to takeoff on runway 19L. Witnesses stated the aircraft climbed steeply after it lifted off with a pitch attitude up to 60°. According to witnesses, the aircraft climbed to 200 to 500 feet agl, before it stalled and descended nose down in a left turn. The aircraft crashed about 300 ft left of and 2000 ft down the rwy. Examination of the aircraft revealed the flaps were full down. The scroll type checklist was positioned at the beginning of the takeoff check. The flight manual recommends a 10 degree flap setting for takeoff and prohibits flap full down takeoff. Review of previous DHC-6 accidents involving flap full down resulted in a steep takeoff climb and excessive pitch attitude followed by a stall. The position of the control lock suggests it may have been in the locked position during the takeoff. The pilot, sole on board, was killed.
Probable cause:
The pilot inadvertently misused the flaps, by failing to set the flaps to the proper setting. The flaps were set full down. This caused the aircraft to pitch up steeply after liftoff. Additionally, the flight control lock was probably installed during some portion, if not the entire flight, which prevented flight control operation. The pilot subsequently failed to maintain adequate flying speed and the aircraft stalled. Contributing factors are the pilot's inattention and his failure to adequately use the checklist.
Findings:
Occurrence #1: loss of control - in flight
Phase of operation: takeoff - initial climb
Findings
1. (c) raising of flaps - not performed - pilot in command
2. (f) inattentive - pilot in command
3. (f) checklist - not used - pilot in command
4. (f) procedures/directives - not followed - pilot in command
5. (f) removal of control/gust lock(s) - inadvertent use - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Swearingen SA226TC Metro II in Washington-Dulles

Date & Time: Dec 18, 1987 at 1936 LT
Type of aircraft:
Operator:
Registration:
N23AZ
Survivors:
Yes
Schedule:
Newark - Washington DC
MSN:
TC-260
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7200
Captain / Total hours on type:
400.00
Aircraft flight hours:
12820
Circumstances:
The aircraft had descended through a cloud layer enroute for the scheduled landing at IAD and according to the crew had picked up some trace rime ice on its wing surfaces. Although pitot and sas (stall avoidance system) heat were used the captain elected not to use engine inlet anti-ice. Just inside the outer marker the left engine lost power followed shortly by the right engine. The captain was able to set the aircraft down in an open field where the gear collapsed during the landing roll. The engines were successfully run-up at the Garrett facility. The flight manual contains a warning and a note stating that engine heat and continuous ignition must be used after leaving icing conditions until the pilot is confident that any significant residual ice will not be ingested into the engines. Ice was found lying beneath the right wing which matched the curvature of the leading edge of the wing. A round conical shaped piece of ice was found along the wreckage path which matched the nose of the propeller spinner.
Probable cause:
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. All engines
2. (f) weather condition - icing conditions
3. (c) in-flight planning/decision - improper - pilot in command
4. (c) anti-ice/deice system - not used - pilot in command
5. (c) inadequate initial training - check pilot
6. (c) inadequate certification/approval, airman - company/operator mgmt
7. (f) wing, skin - ice
----------
----------
Occurrence #3: gear collapsed
Phase of operation: landing - flare/touchdown
Findings
8. (f) terrain condition - open field
9. (f) terrain condition - downhill
10. (f) light condition - dark night
Final Report:

Crash of a Boeing 727-231 on Mt Weather: 92 killed

Date & Time: Dec 1, 1974 at 1110 LT
Type of aircraft:
Operator:
Registration:
N54328
Survivors:
No
Site:
Schedule:
Indianapolis - Columbus - Washington DC
MSN:
20306/791
YOM:
1970
Flight number:
TW514
Crew on board:
7
Crew fatalities:
Pax on board:
85
Pax fatalities:
Other fatalities:
Total fatalities:
92
Captain / Total flying hours:
3765
Captain / Total hours on type:
2899.00
Copilot / Total flying hours:
6205
Copilot / Total hours on type:
1160
Aircraft flight hours:
11997
Circumstances:
Trans World Airlines Flight TW514 was a regularly scheduled flight from Indianapolis, IN (IND), to Washington-National Airport, DC (DCA), with an intermediate stop at Columbus-Port Columbus International Airport, OH (CMH). Flight 514 departed Indianapolis at 08:53 EST and arrived in Columbus at 09:32. The Boeing 727 departed Columbus at 10:24, eleven minutes late. There were 85 passengers and 7 flight crew members aboard the aircraft when it departed Columbus. At 10:36, the Cleveland Air Route Traffic Control Center (ARTCC) informed the crew of Flight 514 that no landings were being made at Washington National Airport because of high crosswinds, and that flights destined for that airport were either being held or being diverted to Dulles International Airport (IAD). At 10:38, the captain of Flight 514 communicated with the dispatcher in New York and advised him of the information he had received. The dispatcher, with the captain's concurrence, subsequently amended Flight 514's release to allow the flight to proceed to Dulles. At 10:42, Cleveland ARTCC cleared Flight 514 to Dulles Airport via the Front Royal VOR, and to maintain FL290. One minute later, the controller cleared the flight to descend to FL230 and to cross a point 40 miles west of Front Royal at that altitude. Control of the flight was then transferred to the Washington ARTCC and communications were established with that facility at 10:48. In the meantime, the flightcrew discussed the instrument approach to runway 12, the navigational aids, and the runways at Dulles, and the captain turned the flight controls over to the first officer. When radio communications were established with Washington ARTCC, the controller affirmed that he knew the flight was proceeding to Dulles. Following this contact, the crew discussed the various routings they might receive to conduct a VOR/DME approach to runway 12 at Dulles. At 10:51, the Washington ARTCC controller requested the flight's heading. After being told that the flight was on a heading of 100 degrees, the controller cleared the crew to change to a heading of 090°, to intercept the 300° radial of the Armel VOR, to cross a point 25 miles northwest of Armel to maintain 8,000 feet, "...and the 300° radial will be for a VOR approach to runway 12 at Dulles." He gave the crew an altimeter setting of 29.74 for Dulles. The crew acknowledged this clearance. The pilots again discussed the VOR/DME approach At 10:55, the landing preliminary checklist was read by the flight engineer and the other crewmembers responded to the calls. A reference speed of 127 kts was calculated and set on the airspeed indicator reference pointers. The altimeters were set at 29.74. The crew then again discussed items on the instrument approach chart including the Round Hill intersection, the final approach fix, the visual approach slope indicator and runway lights, and the airport diagram. At 10:59, the captain commented that the flight was descending from 11,000 feet to 8,000 feet. He then asked the controller if there were any weather obstructions between the flight and the airport. The controller replied that he did not see any significant weather along the route. The captain replied that the crew also did not see any weather on the aircraft weather radar. At 11:01, the controller cleared the flight to descend to and maintain 7,000 feet and to contact Dulles approach control. Twenty-six seconds later, the captain initiated a conversation with Dulles approach control and reported that the aircraft was descending from 10,000 feet to maintain 7,000 feet. He also reported having received the information "Charlie" transmitted on the ATIS broadcast. The controller replied with a clearance to proceed inbound to Armel and to expect a VOR/DME approach to runway 12. The controller then informed the crew that ATIS information Delta was current and read the data to them. The crew determined that the difference between information Charlie and Delta was the altimeter setting which was given in Delta as 29.70. There was no information on the CVR to indicate that the pilots reset their altimeters from 29.74. At 11:04, the flight reported it was level at 7,000 feet. Five seconds after receiving that report, the controller said, "TWA 514, you're cleared for a VOR/DME approach to runway 12." This clearance was acknowledged by the captain. The CVR recorded the sound of the landing gear warning horn followed by a comment from the captain that "Eighteen hundred is the bottom." The first officer then said, "Start down." The flight engineer said, "We're out here quite a ways. I better turn the heat down." At 11:05:06, the captain reviewed the field elevation, the minimum descent altitude, and the final approach fix and discussed the reason that no time to the missed approach point was published. At 11:06:15, the first officer commented that, "I hate the altitude jumping around. Then he commented that the instrument panel was bouncing around. At 11:06:15, the captain said, "We have a discrepancy in our VOR's, a little but not much." He continued, "Fly yours, not mine." At 11:06:27, the captain discussed the last reported ceiling and minimum descent altitude. concluded, "...should break out." At 11:06:42, the first officer said, "Gives you a headache after a while, watching this jumping around like that." At 11:07:27, he said, "...you can feel that wind down here now." A few seconds later, the captain said, "You know, according to this dumb sheet it says thirtyfour hundred to Round Hill --- is our minimum altitude." The flight engineer then asked where the captain saw that and the captain replied, "Well, here. Round Hill is eleven and a half DME." The first officer said, "Well, but ---" and the captain replied, "When he clears you, that means you can go to your ---" An unidentified voice said, "Initial approach, and another unidentified voice said, "Yeah!" Then the captain said "Initial approach altitude." The flight engineer then said, "We're out a --- twenty-eight for eighteen." An unidentified voice said, "Right, and someone said, "One to go." At 11:08:14, the flight engineer said, "Dark in here," and the first officer stated, "And bumpy too." At 11:08:25, the sound of an altitude alert horn was recorded. The captain said, "I had ground contact a minute ago," and the first officer replied, "Yeah, I did too." At 11:08:29, the first officer said, "...power on this.... " The captain said "Yeah --- you got a high sink rate." "Yeah," the first officer replied. An unidentified voice said, "We're going uphill, " and the flight engineer replied, "We're right there, we're on course." Two voices responded, "Yeah!" The captain then said, "You ought to see ground outside in just a minute -- Hang in there boy." The flight engineer said, "We're getting seasick." At 1108:57, the altitude alert sounded. Then the first officer said, "Boy, it was --- wanted to go right down through there, man," to which an unidentified voice replied, "Yeah!" Then the first officer said, "Must have had a # of a downdraft." At 1109:14, the radio altimeter warning horn sounded and stopped. The first officer said, "Boy!" At 11:09:20, the captain said, "Get some power on." The radio altimeter warning horn sounded again and stopped. At 11:09:22, the sound of impact was recorded. After the aircraft left 7,000 feet, the descent was continuous with little rate variation until the indicated altitude was about 1,750 feet. increased about 150 feet over a 15-second period and then decreased about 200 feet during a 20-second period. The recorded altitude remained about 1,750 feet until the airplane impacted the west slope of Mount Weather, Virginia, about 25 nmi from Dulles, at an elevation of about 1,670 feet (509 m). The aircraft was totally destroyed by impact forces and a post crash fire and all 92 occupants were killed.
Probable cause:
The National Transportation Safety Board determines that the probable cause of the accident was the crew's decision to descend to 1,800 feet before the aircraft had reached the approach segment where that minimum altitude applied result of inadequacies and lack of clarity in the air traffic control procedures which led to a misunderstanding on the part of the pilots and of the controllers regarding each other's responsibilities during operations in terminal areas under instrument meteorological conditions. Nevertheless, the examination of the plan view of the approach chart should have disclosed to the captain that a minimum altitude of 1,800 feet was not a safe altitude.
The following contributing factors were reported:
- The failure of the FAA to take timely action to resolve the confusion and misinterpretation of air traffic terminology although the Agency had been aware of the problem for several years,
- The issuance of the approach clearance when the flight was 44 miles from the airport on an unpublished route without clearly defined minimum altitudes,
- Inadequate depiction of altitude restrictions on the profile view of the approach chart for the VOR/DME approach to runway 12 at Dulles International Airport.
Final Report:

Crash of a Douglas DC-8-63CF in New York: 11 killed

Date & Time: Sep 8, 1970 at 1606 LT
Type of aircraft:
Operator:
Registration:
N4863T
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
New York – Washington DC – London
MSN:
45951/414
YOM:
1968
Flight number:
TV863
Crew on board:
11
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
22300
Captain / Total hours on type:
7100.00
Copilot / Total flying hours:
15775
Copilot / Total hours on type:
4750
Aircraft flight hours:
7878
Circumstances:
Approximately 1,500 feet from the initiation of the takeoff roll, the aircraft was observed rotating to an excessively nose-high attitude. The aircraft became airborne about 2,800 feet down the runway after which it continued to rotate slowly upward to an attitude estimated to be between 60° and 90° above the horizontal, at an altitude estimated to be between 300 and 500 feet above the ground. The aircraft rolled about 20° to the right, rolled back to the left until it reached approximately a vertical angle of bank, and then fell to the ground in that attitude. The aircraft was destroyed by impact forces and post impact fire. All 11 crew members, the only occupants of the aircraft, died in the accident.
Probable cause:
The Board determined that the probable cause of this accident was a loss of pitch control caused by the entrapment of a pointed, asphalt-covered object between the leading edge of the right elevator and the right horizontal spar web access door in the aft part of the stabilizer. The restriction to elevator movement, caused by a highly unusual and unknown condition, was not detected by the crew in time to reject the takeoff successfully. However, an apparent lack of crew responsiveness to a highly unusual emergency situation, coupled with the captain's failure to monitor adequately the takeoff, contributed to the failure to reject the takeoff.
Final Report:

Crash of a Howard 500 in Charleston

Date & Time: Jul 10, 1969 at 1948 LT
Operator:
Registration:
N320L
Survivors:
Yes
Schedule:
Washington DC – Dallas
MSN:
500-117
YOM:
1943
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7053
Captain / Total hours on type:
289.00
Circumstances:
While in cruising altitude, en route from Washington-Dulles Airport to Dallas, the crew encountered technical problems with the right engine. Decision was taken to shut down the engine and to feather the propeller. The crew was then cleared to divert to Charleston-Kanawha Airport for an emergency landing. During the final approach, the pilot supervisor interfered verbally in the process and the airplane landed 3,000 feet down the runway 23 which is 5,600 feet long. Unable to stop within the remaining distance, the airplane overran and came to rest in flames on a dirt bank. All seven occupants evacuated safely and the aircraft was destroyed.
Probable cause:
The exact cause of the powerplant failure could not be determined. However, it was reported that the pilot-in-command misjudged distance and speed upon landing.
Final Report:

Crash of a Douglas DC-7 in Washington DC

Date & Time: Jul 30, 1964 at 2102 LT
Type of aircraft:
Operator:
Registration:
N464
Flight Type:
Survivors:
Yes
Schedule:
Washington DC - Washington DC
MSN:
44127
YOM:
1953
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14375
Captain / Total hours on type:
260.00
Circumstances:
The crew was completing a local test flight at Washington-Dulles Airport. Upon landing, the nose gear collapsed and the airplane slid for several yards before coming to rest. All eight occupants were uninjured while the aircraft was considered as damaged beyond repair.
Probable cause:
The crew failed to maintain directional control and the pilot-in-command made an inadequate supervision of flight.
Final Report: