FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07CA040 · Schleicher AS-K13

14 Dec 2006 · Gregory, MI, United States

Schleicher AS-K13 · Accident: in flight encounter with weather on approach

From Richmond Field (69G) to Richmond Field (69G)

Report a problem

Event

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

Schleicher AS-K13

Aircraft type
Schleicher AS-K13
Category
Glider
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
N545TT
Operator
John P. Walker · private individual
Onboard fatalities
Unknown
Route
From Richmond Field (69G), Gregory, MITo Richmond Field (69G), Gregory, 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
Approach · VFR pattern final
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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Clearance, not possible
  • Weather condition › Windshear

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

NTSB narrative

The glider contacted trees while on final approach to land. The pilot reported the accident occurred during his second flight of the day. He reported that he checked the winds prior to takeoff and that the flight was bumpy up to 2,000 feet above ground level (agl) at which point it smoothed out to 3,000 feet agl where he was released from the tow plane. He stated that after a 15 minute flight he returned to the airport where he entered a left hand traffic pattern at 1,000 feet agl for runway 18. The pilot reported that when he entered the traffic pattern he noticed the wind sock was shifting and the glider was losing altitude at a rate that was faster than the previous flight. He stated that because of this, he turned onto base leg sooner than normal. He reported, "Upon turning there was an immediate sense of an inability to penetrate thru the airmass as the glider continued to lose altitude." He stated he lowered the nose of the glider in an attempt to gain airspeed and flew an abbreviated base leg, heading straight for the runway. The pilot reported he then noted a shift in the wind and the glider descended into the 75 foot tall trees northeast of the approach end of the runway. The pilot of the tow plane reported he flew 4 flights on the day of the accident and that during the first 3 flights the winds were from the southwest at less than 15 knots. He reported that for the accident flight the windsock indicated the winds were from the southeast and that the automated weather observing system (AWOS) indicated the winds were from 170 degrees at 8 or 9 knots. He stated that after he landed the windsock indicated the winds had shifted again to the southwest. He stated he checked the AWOS from the Mason-Jewett Airport (TEW), Mason, Michigan, and it was indicating the winds were variable from 160 to 240 degrees at 9 knots gusting to 16 or 20 knots. He reported that this was at the same time that the glider was in the traffic pattern to land. The winds rpeorted at TEW, located 20 miles west-northwest of the accident site at 1317 were from 200 degrees at 5 knots gusting to 14 knots. Twenty minutes prior, the TEW winds were reported as being from 200 degrees at 5 knots. The winds reported at the Howell-Livingston County Airport (OZW), Howell, Michigan, located 15 miles north-northeast of the accident site at 1317 were from 170 degrees at 9 knots. Twenty minutes later the OZW winds had shifted to 200 degrees at 10 knots gusting to 15 knots.

Probable cause

The pilot's unexpected encounter with wind shear and his inability to remain clear of the trees while on final approach to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07CA040
Event ID
20070109X00027
Case number
CHI07CA040
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: c64e5f838c58ede46abd20527a04e386c3d8436eab214bc24c337db3f585cc52; retrieved 2026-09-22T04:08:15.216Z.