CHI03LA214 · Ayres Corporation S2R-G10
Peterson Aerial Spraying Ayres Corporation S2R-G10 · Accident: total loss of engine power (mechanical failure) while maneuvering
From Clarissa Municipal Airport (8Y5) to Staples Municipal Airport (SAZ)
Event
- NTSB case
- CHI03LA214
- 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
Ayres Corporation S2R-G10
- Aircraft type
- Ayres S2
- 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
- N3299A
- Operator
- Peterson Aerial Spraying
- Onboard fatalities
- Unknown
- Route
- From Clarissa Municipal Airport (8Y5), Clarissa, MNTo Staples Municipal Airport (SAZ), Staples, MN
- 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 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 · aerial application
- 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
- Total loss of engine power (mechanical failure)
- 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
- Engine assembly, gear › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The agricultural airplane received substantial damage during a forced landing subsequent to an aerial application. The pilot initiated a climb to the nearest airport when he noticed instrument indications of low oil pressure. About five seconds later, the propeller went into feather and the engine stopped. The pilot stated that he had never landed with a feathered propeller and when he attempted to land in a clearing, he floated across it and into trees at the far end. The examination revealed a separation through the oil jet flange consistent with high cycle fatigue that initiated at several locations along the flange surface. No tool marks were noted in the area. The oil jet flange material was consistent with the specified aluminum alloy.
Probable cause
The fatigue fracture of the oil jet flange resulting in a total engine failure during the aerial application.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA214
- Event ID
- 20030722X01165
- Case number
- CHI03LA214
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 71325881d2c178325b05e6ea88019056525997a3c7828d88002013970e00b53f; retrieved 2026-09-22T08:58:17.816Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "The agricultural airplane received substantial damage during a forced landing subsequent to an aerial application", not that it was destroyed.