FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA146 · Fogg QUICKSILVER MX II

15 Feb 2014 · Holland, MI, United States

Fogg QUICKSILVER MX II · Accident: abnormal runway contact during landing

From Park Township Airport (HLM) to Park Township Airport (HLM)

Report a problem

Event

NTSB case
CEN14LA146
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
Visual Meteorological Cond

Fogg QUICKSILVER MX II

Aircraft type
Fogg QUICKSILVER MX
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
N94567
Operator
Unknown
Onboard fatalities
Unknown
Route
From Park Township Airport (HLM), Holland, MITo Park Township Airport (HLM), Holland, MI
Aircraft age
About 11 years (built 2003)
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 · flare/touchdown
Defining eventThe 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
Abnormal runway contact
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, after a local flight, he decided to land on a snow-covered frozen lake. The airplane landed in 18-inch-deep snow and nosed down shortly after touchdown, which resulted in damage to the fuselage and right wing. The pilot reported that, earlier in the day, he had been flying a powered-parachute (not the accident airplane) from a different area of the same frozen lake that only had 1 to 2 inches of snow cover, which led him to believe it would be safe to land during the accident flight. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's inability to maintain airplane control after inadvertently landing in an area of deep snow on a frozen lake.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA146
Event ID
20140219X54535
Case number
CEN14LA146
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 9bcb06d3cac7578f5eb32ac78c2903a649925913d959e26d3b49b9e5365b3d4e; retrieved 2026-09-15T23:19:52.029Z.