FTW98LA279 · Schweizer 269C
Schweizer 269C · Accident: hard landing
Event
- NTSB case
- FTW98LA279
- 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
- 0
- 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
- 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
- N41TH
- Operator
- Lewis H. Travland · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Landing · flare/touchdown
- 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
- 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
- Pilot in command(cfi) › Touchdown, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a demonstration of an autorotation, the helicopter landed hard. The pilot reported that during the autorotation, after completing a flare, he added 'max' allowable power to initiate a power recovery and directional control was lost. Subsequently, the helicopter landed with a slight yaw. The passenger reported that during the autorotation the pilot stated that 'the spot we would land was visible basically right above the pedals.' The aircraft touched down 'firm,' approximately 90 degrees from the direction of travel. Examination of the helicopter revealed that the tailboom forward attachment fitting was fractured. Both tail rotor blades were attached to the hub and fork; however, one blade was found fractured and separated in the spar root area at the end of the hub spindle, and there was a dent in the leading edge near the tip. The tail rotor drive shaft was found twisted and disengaged from the upper pulley aft drive adapter. Examination of the tailboom forward attachment fitting, P/N:269A2323, and associated parts found that the fracture surface was 'consistent with an overstress failure.' There were 'no signs of preexisting cracks found.'
Probable cause
The improper touchdown executed by the flight instructor, which resulted in the tail rotor impacting the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA279
- Event ID
- 20001211X10099
- Case number
- FTW98LA279
- 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. 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: e76416a6b1b5cae5eba090515e653f20ee2b530b339c82972741056fdd5be8ef; retrieved 2026-09-22T17:46:10.435Z.