Accident Details
Probable Cause and Findings
The pilot's failure to maintain the published minimum descent altitude and not adhering to the published missed approach procedures, which resulted in an in-flight collision with trees and terrain. Factors contributing to the accident were low ceilings and trees.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHT
On January 6, 2006, about 1950 Pacific standard time, a Piper Seneca PA-34-200T, N36107, was destroyed after colliding with trees and terrain at the Skagit Regional Airport (BVS), Burlington, Washington. The airplane is registered to Airpac Airlines, Inc, of Seattle, Washington, and was being operated as "Airpac 32F" a domestic non-scheduled cargo flight operated in accordance with the provisions of Title 14 CFR Part 135. The airline transport pilot, the sole occupant of the airplane, was fatally injured. Instrument meteorological conditions prevailed at the time of the accident. The flight originated at Bellingham, Washington, (BLI) on an instrument flight rules (IFR) flight plan, approximately 15 minutes prior to the accident. The pilot's flight planned destination was BVS.
On January 6, at 2139, Seattle Flight Service Station issued an Alert Notice (ALNOT) after radio and radar contact with the accident aircraft was lost. The following morning, about 0730, the airplane wreckage was located in a heavily wooded area near the approach runway.
The Aviation division of the Washington State Department of Transportation coordinated search and rescue operations for the missing aircraft. DOT personnel reported that search efforts on the evening of the accident were hampered due to fog and low ceilings.
The pilot was completing the third segment of a six-leg itinerary when the accident occurred. The non-scheduled cargo flight normally originates at Boeing Field, Seattle, Washington, as Airpac 32F, with intermediate stops at Friday Harbor, Washington; Bellingham, Washington; Burlington, Washington; Everett, Washington and Portland, Oregon, ultimately terminating back at Boeing Field.
PERSONNEL INFORMATION
The pilot-in-command held an airline transport pilot (ATP) certificate with ratings for airplane multi-engine land, and commercial privileges for airplane single-engine land. The pilot held a ground instructor certificate with advanced and instrument ratings.
The pilot's most recent FAA second-class medical certificate was issued on June 22, 2005, and contained limitations requiring the pilot to wear corrective lenses.
According to the Pilot/Operator accident report (Form 6120.1/2), completed by Airpac Airlines, the pilot had accumulated approximately 4,685 hours total flying time, including 4,589 hours as pilot-in-command (PIC); 1,062 hours as PIC of multi-engine airplanes; 248 hours of actual instrument time and 220 hours of PIC time in make and model.
The report indicated that the pilot had flown 130 hours in the 90-day period preceding the accident, 58 hours in the 30-day period preceding the accident and 1.4 hours in the 24-hour period prior to the accident.
Training records furnished by the operator indicated that the pilot's most recent 14 CFR Part 135 knowledge check, competency check, line check and demonstrated IFR proficiency check were successfully completed on December 6, 2005. The check ride was conducted in a Piper PA-31-350T Navajo.
The pilot's duty day began, as scheduled, at approximately 1700 on the day of the accident.
The pilot had been employed with Airpac Airlines since May of 2004.
AIRCRAFT INFORMATION
The twin engine Piper Seneca PA-34-200T, Serial number 34-7870294 was manufactured in 1978. The airplane was equipped with two Teledyne Continental Motors (TCM) TSIO-360 engines, rated at 200 horsepower. At the time of the accident, the airplane was configured with two pilot seats and the aft cabin area was configured for cargo type operations. In addition to the originally installed instrumentation and avionics, the airplane was equipped with a Garmin GNS 430 global positioning system (GPS). According to the operator, the GPS was certified for VFR operation only, and the unit was placarded accordingly.
The airplane's last inspection, a phase three inspection in accordance with an approved inspection program (AAIP), was completed on January 6, 2006. Maintenance records showed that the airplane's total time at inspection was 7,302 hours. The right engine's total time at inspection was 290.5 hours; the left engine's total time at inspection was also 290.5 hours.
The airplane was equipped for instrument flight rules (IFR) operations. Maintenance records showed that the last altimeter system and altitude reporting equipment test (in accordance with FAR 91.411) was completed on April 8, 2004.
There were no open logbook maintenance discrepancies with the aircraft at the time of the accident.
METEOROLOGICAL INFORMATION
The 1910 METAR weather observation at the Skagit Regional Airport was, in part, visibility 5 statute miles; broken clouds at 100 feet AGL (above ground level); overcast skies at 600 feet AGL.
The 1930 METAR weather observation at the Skagit Regional Airport was, in part, visibility 5 statute miles; broken clouds at 100 feet AGL; overcast skies at 800 feet AGL.
The 1950 METAR weather observation at the Skagit Regional Airport was, in part, visibility 5 statute miles; broken clouds at 100 feet AGL; overcast skies at 800 feet AGL.
The 2010 METAR weather observation at the Skagit Regional Airport was, in part, winds from 170 degrees at 4 knots; visibility 3 statute miles; overcast skies at 200 feet AGL.
According to the U.S. Naval Observatory, official sunset was at 1630, and the end of civil twilight was at 1707.
COMMUNICATIONS/ RADAR DATA
The radar targets attributable to Airpac 32 were identified by transponder code 7026, and began approximately one mile south of the Bellingham Airport. The radar data indicated Airpac 32 tracked a southerly heading from Bellingham to the Skagit Regional Airport. After a continuous climb to 5,100 feet mean sea level (msl), the airplane leveled off briefly (approximately one minute) then began a descent towards the destination airport. The radar track indicated the airplane crossed over the airport at 3,100 feet msl and started a right turn. The turn continued for approximately 360 degrees, in a racetrack type pattern, until the airplane reached the final inbound course for the landing runway. Shortly after reaching the inbound course, radar contact with the aircraft was lost. The last radar position for the aircraft was approximately 6 tenths of a mile (48:29.28 degrees north and 122 26.50 degrees west) from the airport at an altitude of approximately 1000 feet msl. The magnetic bearing from the radar target to the airport was approximately 125 degrees magnetic.
ATC communications:
At 19:36:47, the pilot advised Whidbey approach he was on frequency and climbing through 4,000 feet to 5,000 feet. The approach controller acknowledged the transmission, issued the altimeter setting, and asked the pilot to "...say request at Skagit." The pilot responded, stating that he was going to "...shoot the NDB."
At 19:36:59, the approach controller responded to the pilot stating "...looks like they are IFR" with a broken ceiling of 100 feet and a visibility of five miles.
At 19:37:03, the pilot acknowledged the controller and asked for vectors for the final approach, stating "...if you can get us a um final approach fix that'd be great save us from doing the full turn."
At 19:37:10, the approach controller advised the pilot he was unable to vector him to the final approach fix, stating "Na I don't think I can vector you to the final approach course just when able proceed direct to the Bayview NDB maintain 5,000 expect no delays."
At 19:37:16, the pilot acknowledged the clearance.
At 19:40:35, Whidbey approach cleared the pilot for the approach, stating "Airpac 32 cross the Bayview NDB at or above 3,000 cleared NDB approach runway one zero."
At 19:40:39, the pilot acknowledged the approach controller's clearance.
At 19:46:21, the pilot reported to the approach controller that he was procedure turn inbound. The controller acknowledged the transmission, approved him for a change to advisory frequency and instructed the pilot to report "on deck" via flight service.
At 19:46:29, the pilot acknowledged the controller stating, "Okay wilco Airpac 32 thanks."
At 19:46:56, the pilot reported to Skagit traffic (on Whidbey approach frequency) that he was "on the NDB." The Whidbey approach controller responded, stating "Transmitting Whidbey." This was the last known radio transmission from Airpac 32F.
A complete ATC communication transcript and additional radar data is enclosed in the public docket.
AIRPORT INFORMATION
The Skagit Regional Airport is operated by the Port of Skagit County and serves as the primary airport for both Burlington and Mount Vernon, Washington. The airport has two hard-surfaced asphalt runways, 10/28 and 04/22 magnetic. Runway 10/28 is 5,477 feet long and 100 feet wide. The runway is equipped with medium intensity runway lights (MIRL), runway end identification lights (REIL), and a four-box visual approach slope indicator (VASI) that is located on the left side of runway 10. The runway lights are pilot activated/controlled via the common traffic advisory frequency (CTAF) 123.05.
Aircraft communications at the airport are accomplished via the airport's published common traffic advisory frequency (CTAF) on 123.05. There is no operating air traffic control tower at the airport.
Whidbey Naval Air Station Air Traffic Control provides radar approach/departure control services for the airport on a continuous basis.
There are three non-precision instrument approaches available at the airport, including a Non-Directional Beacon (NDB) and Global Positioning System (GPS) to runway 10, and a GPS to runway 28. The minimum descent altitude/height (MDA) for the straight-in NDB runway 10 approach is 1,240 feet above mean sea level, which is 1,096 feet above the touchdown zone elevation of 144 feet. The procedure turn altitude for the approach is 2,700 feet msl and the inbound cours...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# SEA06FA039