Crash location | Unknown |
Nearest city | Olympia, WA
47.037874°N, 122.900695°W |
Tail number | N222KA |
---|---|
Accident date | 13 Feb 2001 |
Aircraft type | Beech 200 |
Additional details: | None |
On February 13, 2001, approximately 1020 Pacific standard time, a Beech 200, N222KA, registered to the State of Washington and operated by the Aviation Section of the Washington State Patrol on a public-use flight from Yakima, Washington, overran the end of runway 17 during landing following an instrument landing system (ILS) approach to runway 17 at Olympia, Washington. Following the runway overrun, the aircraft's right main landing gear collapsed, and the airplane was substantially damaged. There were no injuries to the airline transport pilot-in-command, commercial second pilot, or 10 passengers aboard the aircraft (all 12 persons aboard were Washington State Patrol employees.) Instrument meteorological conditions were reported at Olympia at 0956 and 1036, and the flight was on an instrument flight rules (IFR) flight plan.
The pilots reported that they received the Olympia weather from Seattle Approach Control upon being handed off to that facility. According to the pilots, the Seattle approach controller advised them that the ceiling was 100 feet variable, and that visibility was 1/4 mile in fog. The pilots reported that the Seattle approach controller then asked their intentions, and that they stated they wanted the ILS runway 17 approach into Olympia. The pilot stated he called for approach flaps approximately 5 miles from HABOR intersection. The pilots reported that the approach controller set them up for a left base intercept of the localizer approximately 3 miles north of HABOR. The pilot reported that the controller assigned him a heading of 200 degrees until localizer intercept, instructed him to descend and maintain 2,500 feet until established, and cleared him for the ILS runway 17 approach. The pilot reported that "It appeared he turned us too late", however, and that the aircraft flew through the localizer. The pilot stated the controller then turned him to a new heading of 140 degrees for localizer intercept, and asked if the pilot wanted to continue the approach. The pilot stated that he replied that he did. The pilot reported that after intercepting the localizer and stabilizing on the localizer and glide slope inside of HABOR, the approach was stable (on course and on glide slope) at approximately 120 knots.
The pilots reported that the second pilot called the approach lights in sight at 100 feet above decision height (DH), and that the second pilot called the runway in sight as the aircraft approached DH. The pilot stated that he looked out and initially did not see the runway, but that "within a matter of seconds" he looked out again and observed the runway numbers and touchdown zone markings. The pilot reported that he then began pulling the power levers to flight idle, and that full flaps were lowered at this time. The pilot stated that he last glanced at his airspeed as the second pilot called the runway and that his recollection was that he was at approximately 115 knots; he stated that this was the last time he recalled his airspeed. The pilot reported that the visibility on final was better than the 1/4 mile being reported (he reported it as about 1/2 mile), and that he did not lose sight of the runway at any time during this phase of the approach.
The pilot reported: "Once we were settling in for landing, I observed the aiming point marks for [runway] 35 approaching rapidly. Once landed I applied max [braking] and full reverse as [the second pilot] put the props full forward. It was apparent at this time that we had excessive speed and were going to run off the end of the runway." The aircraft ran off the end of the runway, collapsing its right main gear and coming to rest on its right wing. The Washington State Patrol operator's report to the NTSB indicated that no mechanical malfunction or failure of the aircraft was involved in the accident.
An FAA inspector from the Seattle, Washington, Flight Standards District Office (FSDO) interviewed the 10 passengers aboard the airplane, the tower controller, and the State Patrol aviation section secretary on duty at the airport at the time of the accident. Most passengers reported that on the accident approach, they first saw the ground at estimated altitudes ranging from 50 feet above ground level (AGL) to 300 feet AGL; one passenger reported not seeing the ground before touchdown. The State Patrol secretary (in the State Patrol hangar 500 feet from the runway) and the tower controller (1,230 feet from the runway) both reported that they did not see the airplane land; the State Patrol secretary reported she could just make out the runway from the hangar, whereas the tower controller reported he could not see the runway from the control tower. The passengers estimated visibility at the airport from "a couple of hundred feet" to less than 1/4 mile (of those who reported visibility estimates, the majority estimated it as 300 to 500 feet.) One passenger also reported that the visibility deteriorated as the airplane progressed down the runway. Three passengers reported that the aircraft floated or landed long, with one reporting that the airplane was just above the level of the VOR tower (located approximately midfield about 750 feet from the runway) as the airplane passed abeam the VOR. All 10 passengers reported that the touchdown was firm, hard, harder than normal, or solid, that the airplane "landed with a thunk", or that the touchdown was "not one of the best he had felt."
Investigators from the NTSB and FAA responded to the accident scene on the day of the accident and performed an on-scene examination of the aircraft and the accident area. The investigators found skid marks on the runway end, starting at a point 376 feet prior to the runway end and continuing in the dirt for 442 feet beyond the end of the runway before terminating at the aircraft. Both of the aircraft's navigation radios were tuned to 111.9 megahertz (MHz), the I-OLM (Olympia runway 17) localizer frequency, with both pilots' horizontal situation indicator (HSI) course deviation indicators (CDIs) set to the ILS final approach course of 172 degrees. Both altimeters were set to 30.20 inches Hg and indicated within 75 feet of the airport elevation of 206 feet. A Jeppesen approach chart dated May 5, 1995 (current at the time of the accident) for the ILS runway 17 approach to Olympia was clipped to the copilot's control wheel. The aircraft's radio altimeter decision height (DH) bug was set to 200 feet, 50 feet below the approach DH of 250 feet AGL. The aircraft's flaps were fully extended. No evidence of mechanical problems with the aircraft was noted.
The 0956 Olympia METAR observation reported weather conditions as: wind from 030 degrees true at 5 knots; visibility 1/4 statute mile in fog; sky obscured with vertical visibility 100 feet; temperature and dew point 0 degrees C; and altimeter setting 30.20 inches Hg. A special observation taken at 1036 reported the same conditions, except for winds from 360 degrees true at 3 knots.
DH on the straight-in ILS runway 17 approach at Olympia is 454 feet above sea level, 250 feet above the touchdown zone elevation of 204 feet. The published minimum visibility for the straight-in ILS approach is 1/2 mile. The State Patrol's operating procedures specify that weather minimums for IFR approaches are as specified by 14 CFR 91.175.
Olympia runway 17 is a 5,419-foot-long, asphalt-surface runway. The runway 17 threshold is displaced 427 feet, leaving a usable landing distance of 4,992 feet. Of this, 3,981 feet are available beyond the runway/glide slope intersection point. The State Patrol's operator's report to the NTSB reported that the runway was wet at the time of the landing. The runway is equipped with an ILS, medium intensity runway lights, and a medium intensity approach lighting system with runway alignment indicator lights (MALSR). The airport is also equipped with an Automated Surface Observing System (ASOS). The Olympia tower controller reported that there were no ILS facility alarms on the day of the accident.
According to records supplied by the State Patrol, the pilot had successfully completed the Beech 200 Pilot Recurrent Course at the FlightSafety International Raytheon Learning Center, Wichita, Kansas, on October 28, 2000, and the copilot had successfully completed the same course at the same location on September 20, 2000. Both pilots' endorsements from this course indicated that they had undergone a flight review according to 14 CFR 61.56(c) and instrument experience according to 14 CFR 61.57(c) during their training. State Patrol records also indicated that at the time of the accident, the aircraft was current on all required inspections to include VOR receiver checks, pitot-static system, altimeter, and transponder system checks required for IFR flight.
The pilot reported the aircraft's gross weight at the time of landing as 11,009 pounds. The "Landing Distance with Propeller Reversing - Flaps 100%" performance chart in the Beech 200 Pilot's Operating Handbook gives the aircraft's approach speed as 99 knots indicated airspeed (KIAS) and its landing distance as approximately 1,100 feet under the following conditions: power retarded to maintain 1,000 feet per minute descent rate on final approach; paved, level, dry surface; approach speed as tabulated (99 KIAS at 11,000 pounds gross weight); maximum braking; condition levers at high idle; propeller controls full forward; power levers maximum reverse after touchdown until fully stopped; temperature 0 degrees C; pressure altitude 0 feet; gross weight 11,000 pounds; tailwind component 5 knots; and no obstacles.
The pilot's failure to attain the proper touchdown point for landing. A factor was weather conditions below published approach minimums.