ERA17LA332 · Robinson Helicopter R22 Beta
Robinson Helicopter R22 Beta and Piper PA 28R-201 · Accident: midair collision during landing
Event
- NTSB case
- ERA17LA332
- 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
Aircraft 1 · Robinson Helicopter R22 Beta
- Aircraft type
- Robinson R22
- 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
- N404TB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clearwater Air Park (CLW), Clearwater, FLTo Clearwater Air Park (CLW), Clearwater, FL
- Aircraft age
- About 12 years (built 2005)
- 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
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Piper PA 28R-201
- Aircraft type
- Piper PA-28
- 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
- N1881H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clearwater Air Park (CLW), Clearwater, FLTo Clearwater Air Park (CLW), Clearwater, FL
- Aircraft age
- About 40 years (built 1977)
- 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
- 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
- Midair collision
- 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 › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A private pilot in a fixed-wing airplane was landing at the airport following a personal flight, and a flight instructor and a pilot receiving instruction were conducting a flight review in a helicopter and practicing maneuvers in the airport traffic pattern. The instructor reported that he or the pilot receiving instruction made radio calls on the common traffic advisory frequency (CTAF) before each turn in the pattern. When the helicopter was 1 mile from the runway, the pilot receiving instruction turned the helicopter onto final approach. After completing a steep approach, the pilot receiving instruction brought the helicopter into a hover about 15 ft above the runway threshold. The airplane pilot stated that he heard a heavy buzzing sound on the CTAF, like a helicopter rotor, and a barely distinguishable word; he scanned for traffic and declared being on downwind. The airplane pilot quickly turned to the base leg of the traffic pattern and then proceeded to land; the airplane then struck the helicopter from behind as the airplane landed on the same runway as the helicopter. The pilots of both aircraft reported scanning for traffic; however, the airplane pilot reported that he did not see the helicopter until about 2 seconds before the collision, while the flight instructor and pilot receiving instruction in the helicopter did not see the airplane before the collision, as the helicopter was oriented down the runway with its tail pointed toward the runway's approach end. Given that the airplane struck the helicopter from behind while landing, it is unlikely that the helicopter pilots were in a position to see and take action to avoid the airplane. Conversely, because of the airplane's position, the airplane pilot had the best opportunity to see and take action to avoid the helicopter.
Postaccident examinations of the radio communication systems in the airplane and helicopter did not reveal any anomalies. The instructor in the helicopter indicated that radio calls were made during every turn while the helicopter was in the airport traffic pattern. The airplane pilot indicated that he was operating on the CTAF and that he was confident his calls on the radio were heard. However, the pilot of another airplane who was about 2 miles west of the airport and was monitoring the airport's CTAF recalled hearing a radio call from the helicopter announcing that it was on a 1-mile final approach to the runway at 500 ft but did not recall hearing any transmissions from the airplane. Thus, given that the airplane pilot's transmissions were not heard, it is likely that he did not adequately transmit the airplane's position while in the airport traffic pattern.
Probable cause
The airplane pilot's inadequate visual lookout, which resulted in an in-flight collision with a helicopter. Contributing to the accident was the airplane pilot's failure to adequately transmit his position while operating in the airport traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA332
- Event ID
- 20170923X01730
- Case number
- ERA17LA332
- 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: 6f7bf57d054efe5daa467ef3ea40ecdcc2993614389dbbbe29fff62435727e2f; retrieved 2026-09-13T18:27:18.746Z.