ATL06LA061 · Ayres S2R-T34
Ayres S2R-T34 · Accident: total loss of engine power (mechanical failure) en route
From Davis Field (3J6) to Davis Field (3J6)
Event
- NTSB case
- ATL06LA061
- 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 S2R-T34
- 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
- N3096H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Davis Field (3J6), Folkston, GATo Davis Field (3J6)
- 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
- En route · climb to cruise
- 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)
- 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
- Compressor assembly, blade › Failure, total
- Compressor assembly, blade › Overtemperature
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 observed black smoke and white sparks from the engine exhaust while climbing between 80 to 100 feet on initial takeoff climb followed by a sudden loss of engine power. The pilot landed straight ahead to none suitable terrain. The landing gear separated and the bottom of the fuselage received structural damage. Examination of the airplane reveled separated turbine blades in the exhaust section of the airplane. The engine was disassembled. The compressor turbine shroud exhibited battering and gouges. The compressor turbine disc blade airfoils were fractured from the root to about three quarters span and exhibited battering and gouging. The disc upstream side blade platforms exhibited circumferential rubbing. The compressor turbine disc was forwarded to the Pratt & Whitney Materials Laboratory for examination under the supervision of Transport Safety Board Canada . The examination revealed the compressor turbine blades failed in overload due to high temperature exposure.
Probable cause
The total loss of engine power due to the failure of the compressor turbine blades due to high temperature exposure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06LA061
- Event ID
- 20060406X00405
- Case number
- ATL06LA061
- 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: bd19dd1cbb3b75e0361e92e8527537b7df62f413a412d37216bd24487b05966f; retrieved 2026-09-21T18:48:26.008Z.