CEN13LA422 · Grumman Aircraft COR-Schweizer G-164A
SLF Air Grumman Aircraft COR-Schweizer G-164A · Accident: loss of control in flight while maneuvering
From Lakes of the North Airport (4Y4) to Lakes of the North Airport (4Y4)
Event
- NTSB case
- CEN13LA422
- 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
Grumman Aircraft COR-Schweizer G-164A
- Aircraft type
- Grumman Aircraft Cor Schweizer G-164
- 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
- N8719H
- Operator
- SLF Air
- Onboard fatalities
- Unknown
- Route
- From Lakes of the North Airport (4Y4), Gaylord, MITo Lakes of the North Airport (4Y4), Gaylord, MI
- Aircraft age
- About 38 years (built 1975)
- 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 137: Agricultural
- 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
- Maneuvering · low-altitude flying
- 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
- Loss of control in flight
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was applying agricultural product on a field, flying toward a line of trees that were about 60 feet in height. The airplane had been loaded with about 200 gallons of chemical, of which about 100 gallons had already been sprayed. Upon completion of the spray run, the airplane impacted the tree line. Postaccident examination of the airplane revealed no mechanical malfunctions or anomalies that would have precluded normal operation.
Probable cause
The pilot's failure to maintain clearance from a line of trees while applying agricultural product to a field.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA422
- Event ID
- 20130719X60101
- Case number
- CEN13LA422
- 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, 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: 5eeda9e86e44529099fa868a5dcb798ed314c0a19ee4671f572601ffb2740afd; retrieved 2026-09-15T22:15:29.531Z.