 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Bjc local controller reported that a BE35 in the traffic pattern experienced wake turbulence from an H60 operating on a parallel runway.
| Attributes | |
| ACN | 1539810 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BJC.Tower |
| State Reference | CO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Bonanza 35 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff Initial Approach |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | S-70/UH-60 Blackhawk/Seahawk/Pavehawk/Knighthawk |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb Takeoff |
| Flight Plan | VFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
A bonanza BE35 was in right closed traffic for options (doing full stop taxi backs) on runway 30R; with an H60 in left closed traffic for options on runway 30L (doing stop and goes). I believe that the BE35 was cleared for takeoff on 30R while the H60 was on the go for 30L. I had at least one other aircraft in the traffic pattern for 30R; and I gave the position of the H60 and provided a wake turbulence advisory to that aircraft.at that point; the BE35 mentioned they had encountered wake turbulence from the H60 earlier and 'the threat is real.' I acknowledged; continued to issue wake turbulence/traffic advisories; and all the aircraft continued to operate in the pattern without further incident.this event reminds me that; as controllers; we should always remain vigilant for potential wake turbulence situations. While wake turbulence separation/advisories are not always mandatory; in some instances; controllers still have a responsibility to try to anticipate those situations where wake turbulence may be a factor and try to issue those advisories in a timely manner (in accordance with other higher priority duties). I try to do that as much as feasible; but perhaps overlooked issuing it to the BE35 with their takeoff clearance in this instance.I am glad that the pilot mentioned their encounter to raise awareness of wake turbulence risks and allow others to learn from the event.
Original NASA ASRS Text
Title: BJC Local Controller reported that a BE35 in the traffic pattern experienced wake turbulence from an H60 operating on a parallel runway.
Narrative: A Bonanza BE35 was in right closed traffic for options (doing full stop taxi backs) on Runway 30R; with an H60 in left closed traffic for options on Runway 30L (doing stop and goes). I believe that the BE35 was cleared for takeoff on 30R while the H60 was on the go for 30L. I had at least one other aircraft in the traffic pattern for 30R; and I gave the position of the H60 and provided a wake turbulence advisory to that aircraft.At that point; the BE35 mentioned they had encountered wake turbulence from the H60 earlier and 'the threat is real.' I acknowledged; continued to issue wake turbulence/traffic advisories; and all the aircraft continued to operate in the pattern without further incident.This event reminds me that; as controllers; we should always remain vigilant for potential wake turbulence situations. While wake turbulence separation/advisories are not always mandatory; in some instances; controllers still have a responsibility to try to anticipate those situations where wake turbulence may be a factor and try to issue those advisories in a timely manner (in accordance with other higher priority duties). I try to do that as much as feasible; but perhaps overlooked issuing it to the BE35 with their takeoff clearance in this instance.I am glad that the pilot mentioned their encounter to raise awareness of wake turbulence risks and allow others to learn from the event.
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.