Beechcraft A100 N700NC
5 January 2006 · Sault Ste Marie, Michigan, United States · No injuries
Summary
On 5 January 2006 at about 07:00 local time, a Beechcraft A100 registered N700NC, operated by North Country Aviation, Inc, was involved in an accident near Sault Ste Marie, Michigan, United States. 3 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 07:00
- Classification
- Accident
- Location
- Sault Ste Marie, Michigan, United States
- Nearest airport
- Sault Ste Marie/Sanderson (ANJ)
- Coordinates
- 46.4792, -84.3683
- Aircraft
- Beechcraft A100
- Registration
- N700NC
- Category
- Airplane
- Engines
- 2
- Operator
- North Country Aviation, Inc
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Positioning
- Phase of flight
- Not recorded
- Route
- Traverse City → Sault Ste Marie
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night/Dark
- NTSB number
- CHI06LA062
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 0 | 0 | 0 | 3 |
Probable cause
The inadequate in-flight decision to continue the approach to land, directional control not maintained, and the contaminated runway. Contributing factors were flight to destination alternate not performed, a notice to airman not issued by airport personnel relating to snow/slush contamination of the runway, and the snow bank that the airplane impacted during the landing.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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 nonprecision 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.
Quoted verbatim from the NTSB record.
Other Beechcraft A100 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 6 Nov 2007 | Beechcraft A100 | Chino, California, United States | Rhb-Jmj LLC | Fatal | 2 |
| 23 Nov 2008 | Beechcraft A100 | God's Lake Narrows, Canada | Sky North Air | Minor injuries | - |
| 22 Aug 2008 | Beechcraft A100 | Moab, Utah, United States | Leavitt Group Wings LLC | Fatal | 10 |
| 17 Mar 2003 | Beechcraft A100 | Carrollton, Georgia, United States | - | No injuries | - |
| 18 Oct 2010 | Beechcraft A100 | Palestine, Texas, United States | Trinity River Authority of Texas | No injuries | - |
| 23 Jun 2010 | Beechcraft A100 | Quebec City, Canada | Aeropro | Fatal | 7 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Jan 2006 | Univar ERCOUPE | Howell, Michigan, United States | - | No injuries | - |
| 23 Aug 2006 | Frick QUESTAIR Q20 | Big Rapids, Michigan, United States | - | Fatal | 1 |
| 7 Mar 2006 | Beechcraft J35 | Holland, Michigan, United States | - | Fatal | 2 |
| 16 Apr 2006 | Palulis John EXEC 162F | Kalkaska, Michigan, United States | - | No injuries | - |
| 7 Mar 2006 | Piper PA-28-180 | Holly, Michigan, United States | Mark U. Heinl | No injuries | - |
| 8 Jun 2006 | Beechcraft B36TC | Gregory, Michigan, United States | - | Fatal | 1 |