FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA397 · Weatherhead Peter L STOL CH 701

29 Jun 2009 · Hayward, WI, United States

Weatherhead Peter L STOL CH 701 · Accident: hard landing

From Sawyer County Airport (HYR) to Sawyer County Airport (HYR)

Report a problem

Event

NTSB case
CEN09CA397
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

Weatherhead Peter L STOL CH 701

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
N861SD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sawyer County Airport (HYR), Hayward, WITo Sawyer County Airport (HYR), Hayward, WI
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 · 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
Hard landing
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
  • Personnel issues › Task performance

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

NTSB narrative

The pilot had purchased the airplane on the day of the accident. Prior to the flight, the pilot obtained a wind check from an employee at a local fixed base operator. The employee informed the pilot the wind was from 320 degrees at 10 to 12 knots and gusting to 16 knots. After departure, the pilot "found the winds to be much worse and had a hard time controlling the 1,000 [pound] gross weight plane." After several attempts to land on the different runways at the airport, the pilot elected to land the airplane in a field short of runway 02 (5,003 feet long by 100 feet wide). During the approach, the pilot flared the airplane 15 to 20 feet above the ground and the airplane "just sank." The airplane landed hard and the left main landing gear separated. In addition, the nose landing gear collapsed, and the airplane nosed over and came to rest inverted. The pilot had no prior experience in the accident airplane make and model prior to this flight.

Probable cause

The pilot's improper flare resulting in a hard landing during gusty wind conditions. Contributing to the accident was the pilot's lack of experience with the accident airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA397
Event ID
20090630X90827
Case number
CEN09CA397
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: 63e641d1a6a489a3674192c3587f01b02001c4f00ee63c23624d2341f0b351f7; retrieved 2026-09-15T11:39:13.467Z.