FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA115 · Piper PA-28R-200

28 Jan 2015 · West Palm Beach, FL, United States

Palm Beach Flight Training Piper PA-28R-200 and Palm Beach Helicopters Robinson Helicopter R22 BETA · Accident: midair collision on approach

Report a problem

Event

NTSB case
ERA15LA115
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 · Piper PA-28R-200

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
N54380
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), West Palm Beach, FLTo Palm Beach County Park Airport (LNA), West Palm Beach, FL
Aircraft age
About 42 years (built 1973)
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
Approach · VFR pattern final
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
Minor

Aircraft 2 · 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
N475AT
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), West Palm Beach, FLTo Palm Beach County Park Airport (LNA), West Palm Beach, FL
Aircraft age
About 18 years (built 1997)
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
Approach · VFR pattern final
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 › Action/decision

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

NTSB narrative

The designated pilot examiner (DPE) and the commercial pilot on board the airplane were performing left traffic patterns during a checkride. A helicopter was simultaneously performing right traffic patterns to the same runway. Throughout the flight, the DPE and pilot had observed the accident helicopter and other helicopters in the right traffic pattern completing their approaches parallel to and to the right side of the runway. The airplane was on the left downwind leg of the traffic pattern, with the commercial pilot preparing for a simulated power-off landing. In light of the previously-observed helicopter operations to the right side of the runway, the DPE advised the pilot that the airplane would remain clear of the helicopters and to continue the approach and landing. The helicopter, however, was established on a shallow, final approach leg of the traffic pattern for a run-on landing. Upon entering the turn from the downwind leg and while on the final approach leg of the traffic pattern for landing, the DPE's view of the accident helicopter was blocked by the cabin and right wing.

The airplane overtook the helicopter from above, and the aircraft collided. The helicopter entered a rapid, controlled descent to the runway. The airplane completed a go-around and subsequently landed safely.

Review of recorded radio communications revealed that the pilots in the airplane transmitted position reports for the crosswind and downwind legs of the traffic pattern only, but did not announce their intentions to conduct, or the airplane's entry into, the simulated power-off landing maneuver. The helicopter pilots transmitted position reports on the downwind, base, and final legs of the traffic pattern, but before the accident landing approach, announced only that the helicopter was "turning final." The helicopter pilots provided no specificity about the shallow approach or performing a run-on landing to the runway surface.

Other helicopters operating in the traffic pattern on the day of the accident had conducted their operations to the grass on the right side of the runway. On the previous approach, the accident helicopter pilots had announced their intention to land the helicopter in the grass abeam the runway. The lack of explicit communication from the helicopter pilots regarding their intentions resulted in the helicopter being in a position that was unexpected to the airplane pilots. In the absence of any information to the contrary, the airplane pilots likely assumed that the accident helicopter would continue to remain clear of the runway and the extended runway centerline, as it and other helicopters had done during previous approaches. This likely lowered the airplane pilots' vigilance in maintaining visual contact with the helicopter throughout the approach for landing.

Probable cause

The failure of the airplane pilots to maintain an adequate visual lookout for known traffic in the traffic pattern, which resulted in a midair collision. Contributing to the accident was the failure of the airplane pilots to announce their intentions before landing, and the helicopter pilots' lack of specificity in their radio communications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA115
Event ID
20150129X05038
Case number
ERA15LA115
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: bf9e367e9a5f1b4b8be690f4e0fd5a2b6b907aede6aa1852d0446226d0ef292b; retrieved 2026-09-13T18:23:37.482Z.