FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06LA062 · Beech A100

5 Jan 2006 · Sault Ste Marie, MI, United States

North Country Aviation Beech A100 · Accident: loss of control on ground/water during landing

From Cherry Capital Airport (TVC) to Sault Ste Marie Municipal Airport Sanderson Field (ANJ)

Report a problem

Event

NTSB case
CHI06LA062
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech A100

Aircraft type
Beechcraft 100
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N700NC
Onboard fatalities
Unknown
Route
From Cherry Capital Airport (TVC), Traverse City, MITo Sault Ste Marie Municipal Airport Sanderson Field (ANJ), Sault Ste Marie, MI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Directional control, not maintained
  • Pilot in command › In-flight planning/decision, inadequate
  • Runway/landing area condition › Slush covered
  • Runway/landing area condition › Snow covered

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06LA062
Event ID
20060629X00847
Case number
CHI06LA062
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 7589f398dc57a09a1b8b07107c30b0f5ece5c8a89d35004348750d0de320ba1b; retrieved 2026-09-22T05:10:18.095Z.