Accident Details
Probable Cause and Findings
The pilot's failure to maintain an adequate altitude and descent rate during a night visual approach. Dark night conditions and mountainous terrain are factors in the accident.
Aircraft Information
Registered Owner (Historical)
Analysis
This report was modified on January 6, 2008.
HISTORY OF FLIGHT
On February 6, 2007, at 2104 mountain standard time, a Beech 200 King Air airplane, N45MF, registered to and operated by Metro Aviation, Inc., of Shreveport, Louisiana, collided with sparsely populated mountainous terrain approximately 13 nautical miles (nm) north-northwest of the Gallatin Field Airport (BZN), Belgrade, Montana. The Emergency Medical Services (EMS) positioning flight was operated under the provisions of 14 Code of Federal Regulations (CFR) Part 91, and an instrument flight rules (IFR) flight plan was in effect. The airplane sustained substantial damage and the three occupants, an airline transport pilot, flight paramedic and flight nurse, were killed. The air ambulance was under contract to Benefis Healthcare/Mercy Flight, Great Falls, Montana. The flight departed Great Falls International Airport, Great Falls, Montana, at 2040 with an intended destination of BZN (approximately 103 nm from the departure airport). Instrument meteorological conditions prevailed at the departure airport and dark night visual meteorological conditions prevailed at the destination airport.
A review of the Air Traffic Control (ATC) transcripts for the flight indicated that radio communications with the airplane was lost shortly after the pilot was cleared for the visual approach to runway 12 at BZN.
At 2108 the Gallatin County Sheriff's Office received reports of a downed aircraft.
The wreckage was located about 2230 that evening approximately 80 feet below the peak of a ridge that rose to an elevation of approximately 5,700 feet. From the first identified point of contact with terrain, the debris path tracked over the crest of the ridge and continued down the opposing side, in a south-southeast direction, for approximately 1,575 feet.
Satellite based flight-tracking data (OuterLink) provided by the Operator indicated the airplane started a descent, from 15,000 feet mean sea level (MSL), approximately 42 nm north of the airport. The last data transmission from the airplane was received approximately six minutes later in the general area where the wreckage was located.
PERSONNEL INFORMATION
Pilot-in-Command (PIC)
At the time of the accident, the PIC, age 59, held an airline transport pilot (ATP) certificate with a rating for airplane multiengine land, a commercial pilot certificate with a rating for airplane single-engine land and a type rating in the BE-300 King Air. The pilot's most recent Federal Aviation Administration (FAA) second-class airman medical certificate was issued on November 10, 2006, with the limitation that he must wear corrective lenses.
Personnel records maintained by the operator indicated that Metro Aviation hired the pilot in November of 1999. Preceding his employment with Metro Aviation, the pilot was employed by Lynch Flying Service (beginning in 1996) as an air ambulance pilot.
Company personnel records revealed that the pilot had accumulated 17,608 hours total flying time, which included 1,318 hours PIC in the King Air 200. The pilot had flown 66 hours in the previous 90 days, 45 hours in the previous 30 days and approximately 25 minutes (the accident flight) in the previous 24 hours.
Training records indicated that the pilot successfully completed initial King Air (BE90 and 100) training in March of 1996, while employed by Lynch Flying Service of Billings, Montana.
On April 2, 2000, the pilot successfully completed King Air 200 initial/upgrade training with SimuFlite in Dallas, Texas. The completion of the course, which included ground and simulator training, qualified the pilot as PIC for the King Air 200. In conjunction with the King Air 200 curriculum at SimuFlite, the pilot completed King Air BE90 and A100 recurrent and differences training.
The pilot's most recent recurrent training for the King Air 200 was successfully completed with SimuFlite, in Dallas, Texas, on March 31, 2006. The recurrent training included ground and simulator training and fulfilled the recurrent Part 135 pilot testing requirements.
The pilot's most recent Part 135 line check and IFR proficiency check were successfully completed on October 12, 2006.
Flight and Duty Time
The accident date, February 6, 2007, was the pilot's fifth consecutive duty day of a seven day rotation cycle. His duty day began at 2100 hours and was scheduled to end at 0700 on February 7. The accident flight was the pilot's first flight of the shift. Flight and duty times for the 5 days preceding the accident were:
On February 5, the pilot's duty day began at 1900 and ended at 0700 the following morning. There were no flight operations during the pilot's duty day.
On February 4 the pilot's duty day began at 1900, and ended at 0700 the following morning. The pilot completed one flight (.8 hours) during the duty period.
On February 3, the pilot's duty day began at 1900, and ended at 0700 the following morning. There were no flight operations during the pilot's duty day.
On February 2, the pilot's duty day began at 1900, and ended at 0700 the following morning. There were no flight operations during the pilot's duty day.
On February 1, the pilot was not on duty.
In the six months preceding the accident, the pilot flew a total of 73.4 hours.
Review of pilot records, and subsequent conversations with the operator, indicated the pilot had flown this particular route of flight and was familiar with the terrain.
AIRCRAFT INFORMATION
The accident airplane, a Beech King Air 200 (serial number BB-234) was manufactured in 1977 and, since the date of manufacture, had accumulated 5,992 total flight hours. The airplane was equipped with two Pratt & Whitney Canada turbo propeller PT6A-41 engines.
The airplane was being maintained in accordance with the manufacture's inspection program. Review of the aircraft logbooks revealed that the airplane's most recent inspection, a phase four inspection, was completed on September 21, 2006, at 5,827 total flight hours. There were no reported open maintenance discrepancies with the airplane at the time of the accident.
The airplane was equipped with a Bendix/King Enhanced Ground Proximity Warning System (EGPWS). The EGPWS is classified as a class B Terrain Awareness and Warning System (TAWS). The EGPWS is a terrain warning system that provides relevant real-time terrain information. The system evaluates the aircraft flight parameters and compares it with an onboard terrain, obstacle and airport database. When the system predicts potential conflicts between the aircraft and terrain it alerts the flight crew of the conflict(s) via audio caution. The system incorporates an inhibit switch in the cockpit. When engaged by the pilot, the switch will silence terrain alerts generated by the system. The airplane was not equipped with a TAWS graphic display.
Post accident data recovery from the component's non-volatile memory was unsuccessful due to the extent of damage sustained during the impact sequence.
METEOROLOGICAL INFORMATION
The closest weather observation facility to the accident site was the destination airport, Gallatin Field Airport, Belgrade, Montana, located approximately 13 nm from the accident site at an elevation of 4,471 feet msl. The airport is equipped with an Automated Surface Observing System (ASOS). The following weather observations (METAR format) were issued surrounding the time period of the accident:
On February 6, at 2056, the observation was, in part, wind from 300 degrees at 4 knots, visibility unrestricted at 10 miles, overcast ceiling at 11,000 feet, temperature 3 degrees Celsius (C), dew point minus 1 degrees C, altimeter 30.30 inches of Hg.
At 2145, the observation was, in part, wind from 260 degrees at 4 knots, visibility unrestricted at 10 miles, overcast ceiling at 11,000 feet, temperature 4 degrees C, dew point minus 1 degrees C, altimeter 30.01 inches of Hg.
The weather observation system at the Great Falls Airport reported the following weather observations:
At 1953, the observation was, in part, wind from 040 degrees at 7 knots, visibility 7 miles, overcast ceiling at 500 feet, temperature minus 8 degrees C, dew point minus 9 degrees C, altimeter 30.13 inches of Hg.
At 1900, Salt Lake Center (ZSLC) received a pilot weather report (PIREP) from the pilot of a Cessna single engine airplane that was 6 nm west of Great Falls at 6,000 feet. The pilot reported light to moderate clear icing with an outside air temperature of 1 degrees C.
According to the U.S. Naval Observatory, Department of Astronomical Applications, the phase of the moon was wanin gibbous (just past full) with 82% of the moons visible disk illuminated. Moonrise was at 2234.
COMMUNICATIONS
At 1959, the pilot contacted, by telephone, the Great Falls Automated Flight Service Station (AFSS) and obtained an abbreviated preflight briefing for an IFR flight from Great Falls to BZN. During the briefing, the pilot declined current weather synopsis information.
At 2010, the pilot contacted, by telephone, the Great Falls AFSS and filed two IFR flight plans, Great Falls to BZN and a return flight from BZN to Great Falls.
At 2039, Great Falls Air Traffic Control Tower (ATCT) cleared N45MF for takeoff, and at 2042 the aircraft was radar identified and cleared to 15,000 feet. At 2056 (16 minutes after takeoff) the pilot of N45MF stated to ATC that the BZN airport was "in sight." At 2057, the pilot was cleared to descend at his discretion from 15,000 feet to 13,000 feet. The pilot acknowledged the clearance and stated "…I've got the airport in sight at BZN requesting a visual approach." At 2100 the pilot was cleared for the visual approach to the BZN airport. At 2101:01 ATC radar services for the flight were terminated and the pilot was instructed by Center to contact BZN Tower. At 2101:21 the pilot contacted BZN Tower. The pilot stated "BZN tower lifeguard King Air ...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# SEA07FA051