37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1740610 |
Time | |
Date | 202004 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | FXE.Tower |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | None |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Helicopter |
Flight Phase | Initial Climb |
Flight Plan | VFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 92 Flight Crew Total 313 Flight Crew Type 56 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Miss Distance | Horizontal 0 Vertical 50 |
Narrative:
My instructor and I were doing touch and goes in the right pattern. We were cleared for the touch and go in the downwind at roughly midfield and performed a standard squared approach. The landing was normal and we continued the takeoff as planned. Just after becoming airborne; we noticed a helicopter taking off from the taxiway to our right. I pulled power and leveled flight around 100 ft. The helicopter continued to climb on its heading and crossed from our right wing to our left wing directly above us at what looked like less than 50 ft. Separation. After regaining sight of the helicopter off our left wing; I returned to climb configuration. A few seconds later the helicopter appeared to be in a slight bank back to the right into our flight path. I turned slightly to the right and continued climb. A few more seconds passed and the helicopter turned steeply directly at us forcing me to dive right immediately. All of this happened prior to reaching 700 ft. The helicopter passed behind us and left the airspace.while I focused on flying the plane; my instructor handled the radios. Tower responded that the helicopter was to remain west of the field. At this point the helicopter pilot called in saying he had us in sight from the beginning. I do not believe this is possible. I had to drastically change course three times in the span of about 40 seconds to prevent a collision. Two of these maneuvers I would consider highly inappropriate at such low altitudes; at night; in a densely populated area if it had not been for the [urgent] situation the helicopter pilot put us in.at the conclusion of my flight; I called the tower phone number to clarify what happened. The controller told me that the helicopter had been cleared for a 'coded departure' from a taxiway. This departure path was supposed to takeoff to the southwest and keep the aircraft west of the field. Due to winds at the time; the pilot decided to takeoff to the northeast instead. It is unclear whether this was communicated to tower. I believe this miscommunication between tower and the other pilot led to our initial near miss. The following two incidents however were entirely due to the helicopter pilot performing turns that put us back on a collision path. This is especially concerning since the other pilot claimed to have us in sight from the beginning.
Original NASA ASRS Text
Title: Pilot reported a NMAC with a helicopter in the traffic pattern.
Narrative: My instructor and I were doing touch and goes in the right pattern. We were cleared for the touch and go in the downwind at roughly midfield and performed a standard squared approach. The landing was normal and we continued the takeoff as planned. Just after becoming airborne; we noticed a helicopter taking off from the taxiway to our right. I pulled power and leveled flight around 100 ft. The helicopter continued to climb on its heading and crossed from our right wing to our left wing directly above us at what looked like less than 50 ft. separation. After regaining sight of the helicopter off our left wing; I returned to climb configuration. A few seconds later the helicopter appeared to be in a slight bank back to the right into our flight path. I turned slightly to the right and continued climb. A few more seconds passed and the helicopter turned steeply directly at us forcing me to dive right immediately. All of this happened prior to reaching 700 ft. The helicopter passed behind us and left the airspace.While I focused on flying the plane; my instructor handled the radios. Tower responded that the helicopter was to remain west of the field. At this point the helicopter pilot called in saying he had us in sight from the beginning. I do not believe this is possible. I had to drastically change course three times in the span of about 40 seconds to prevent a collision. Two of these maneuvers I would consider highly inappropriate at such low altitudes; at night; in a densely populated area if it had not been for the [urgent] situation the helicopter pilot put us in.At the conclusion of my flight; I called the Tower phone number to clarify what happened. The Controller told me that the helicopter had been cleared for a 'coded departure' from a taxiway. This departure path was supposed to takeoff to the southwest and keep the aircraft west of the field. Due to winds at the time; the pilot decided to takeoff to the northeast instead. It is unclear whether this was communicated to Tower. I believe this miscommunication between Tower and the other pilot led to our initial near miss. The following two incidents however were entirely due to the helicopter pilot performing turns that put us back on a collision path. This is especially concerning since the other pilot claimed to have us in sight from the beginning.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.