Traverse City – Sault Sainte Marie
Flight / Schedule
Traverse City – Sault Sainte Marie
Aircraft
Beechcraft 100 King AirRegistration
N700NC
MSN
B-138
Year of Manufacture
1972
Operator
North Country AviationDate
January 2, 2006 at 02:00 AM
Type
CRASHFlight Type
Ambulance
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Sault Sainte Marie Michigan
Region
North America • United States of America
Coordinates
46.4977°, -84.3477°
Crash Cause
Human factor
Narrative Report
On January 2, 2006 at 02:00 AM, Traverse City – Sault Sainte Marie experienced a crash involving Beechcraft 100 King Air, operated by North Country Aviation, with the event recorded near Sault Sainte Marie Michigan.
The flight was categorized as ambulance and the reported phase was landing (descent or approach) at a airport (less than 10 km from airport) crash site.
3 people were known to be on board, 0 fatalities were recorded, 3 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 1, crew fatalities: 0, passengers on board: 2, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. The airplane, operated as an emergency medical flight, received substantial damage when it veered off the edge of runway 32 (5,235 feet long by 100 foot wide asphalt, slush and snow covered) and impacted a snow bank during landing roll at a non 14 CFR Part 139 airport. Night instrument meteorological conditions prevailed at the time of the accident. The pilot stated that during a non precision approach while two miles from the runway, he observed it to be completely covered in snow and slush. He continued the approach and upon touchdown the airplane decelerated in deep slush and veered to the left after a rollout of 1,200 feet. The pilot reported that prior to accepting the emergency medical flight, he obtained a weather briefing from a flight service station during which time no notices to airman (NOTAMs) existed that pertained to the destination airport. The pilot reported that he knew the airport was getting rain and was expecting the runway to be clear. He was surprised that the runway was covered with heavy slush. The airport manager stated that the runway was covered with wet, slushy snow as there had been periods of wet snow and rain that occurred late the previous day and evening of the accident. The airport weather observation recorded the presence of light snow in a period of approximately 24 hours before the accident. The pilot "wondered" why no NOTAM was issued relating to the runway condition. The Airport Facility Directory and the FAA's web site provides a list of 14 CFR Part 139 airports which are inherently required to issue NOTAMs. However, Advisory Circular 150/5200-28C states, the management of a public use airport is expected to make known, as soon as practical, any condition on or in the vicinity of an airport, existing or anticipated, that will prevent, restrict, or present a hazard during the arrival or departure of aircraft. Airport management is responsible for observing and reporting the condition of airport movement areas. Public notification is usually accomplished through the NOTAM system. The Aeronautical Information Manual, states that NOTAM information is information that could affect a pilot's decision to make a flight. It includes information such as airport or primary runway closures, changes in the status of navigational aids, ILS's, radar service availability, and other information essential to planned en route, terminal, or landing operations.
Aircraft reference details include registration N700NC, MSN B-138, year of manufacture 1972.
Geospatial coordinates for this crash are approximately 46.4977°, -84.3477°.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
The airplane, operated as an emergency medical flight, received substantial damage when it veered off the edge of runway 32 (5,235 feet long by 100 foot wide asphalt, slush and snow covered) and impacted a snow bank during landing roll at a non 14 CFR Part 139 airport. Night instrument meteorological conditions prevailed at the time of the accident. The pilot stated that during a non precision approach while two miles from the runway, he observed it to be completely covered in snow and slush. He continued the approach and upon touchdown the airplane decelerated in deep slush and veered to the left after a rollout of 1,200 feet. The pilot reported that prior to accepting the emergency medical flight, he obtained a weather briefing from a flight service station during which time no notices to airman (NOTAMs) existed that pertained to the destination airport. The pilot reported that he knew the airport was getting rain and was expecting the runway to be clear. He was surprised that the runway was covered with heavy slush. The airport manager stated that the runway was covered with wet, slushy snow as there had been periods of wet snow and rain that occurred late the previous day and evening of the accident. The airport weather observation recorded the presence of light snow in a period of approximately 24 hours before the accident. The pilot "wondered" why no NOTAM was issued relating to the runway condition. The Airport Facility Directory and the FAA's web site provides a list of 14 CFR Part 139 airports which are inherently required to issue NOTAMs. However, Advisory Circular 150/5200-28C states, the management of a public use airport is expected to make known, as soon as practical, any condition on or in the vicinity of an airport, existing or anticipated, that will prevent, restrict, or present a hazard during the arrival or departure of aircraft. Airport management is responsible for observing and reporting the condition of airport movement areas. Public notification is usually accomplished through the NOTAM system. The Aeronautical Information Manual, states that NOTAM information is information that could affect a pilot's decision to make a flight. It includes information such as airport or primary runway closures, changes in the status of navigational aids, ILS's, radar service availability, and other information essential to planned en route, terminal, or landing operations.
Cause: Human factor
Occupants & Outcome
Crew On Board
1
Passengers On Board
2
Estimated Survivors
3
Fatality Rate
0.0%
Known people on board: 3
Operational Details
Schedule / Flight
Traverse City – Sault Sainte Marie
Operator
North Country AviationFlight Type
Ambulance
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Region / Country
North America • United States of America
