FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA432 · Schweizer 269C-1

18 Aug 2010 · Titusville, FL, United States

Bristow Academy Schweizer 269C-1 · Accident: hard landing during autorotation

From Space Coast Regional Airport (KTIX) to Space Coast Regional Airport (KTIX)

Report a problem

Event

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

Schweizer 269C-1

Aircraft type
Schweizer 269
Category
Helicopter
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
N1542D
Onboard fatalities
Unknown
Route
From Space Coast Regional Airport (KTIX), Titusville, FLTo Space Coast Regional Airport (KTIX), Titusville, FL
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
Autorotation
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 › Action/decision

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

NTSB narrative

The flight instructor reported that during the helicopter instructional flight, hovering, straight-ahead, and 180-degree-turn autorotations were performed. The flight instructor's remedial actions typically included adjustment of pitch attitude to maintain the target airspeed, or collective adjustment to keep the rotor rpm in the normal operating range. During an autorotation with turn initiated by the student, the flight instructor took control of the helicopter but allowed the rotor rpm to decay below the lower limit. He adjusted collective and throttle, and initiated a decelerative flare to build rotor rpm, but the rotor rpm continued its decay. The flight instructor was unable to arrest the helicopter's descent, and the helicopter impacted the ground on the back of the skids, pitched forward and rolled over, which resulted in substantial damage to the fuselage, tailboom, and both the main and tail rotor systems. No preexisting mechanical anomalies were noted with the helicopter.

Probable cause

The instructor's delayed remedial action, which resulted in a loss of rotor rpm and a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA432
Event ID
20100818X63315
Case number
ERA10CA432
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: 3cb8963cfe7e7d9d7131bfaacfbbb3795bd3d4a2b0105e43a7427ac1ae11d6e4; retrieved 2026-09-15T14:52:15.886Z.