37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1558721 |
Time | |
Date | 201807 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Helicopter |
Flight Phase | Cruise |
Route In Use | None VFR Route |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Light Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working the local and helicopter positions combined at dca ATC. I have been cpc/fpl for [a short time].I accepted a handoff from potomac TRACON on aircraft X 2 miles west of ZZZ. Aircraft X contacted dca tower and requested to fly route 1-Route 4 -ZZZ1 and then to ZZZ2. I radar contacted aircraft X; approved the request and issued the altimeter.aircraft Y called on a seven mile final to dca and requested to land on runway xx. I then I cleared aircraft Y to land.note. My standard practice for helicopters flying the dca helicopter route is to issue any pertinent landing traffic by the time the helicopters pass over the south capitol street bridge.aircraft X asked if I had issued traffic on the aircraft landing runway xx. I thought I had applied my standard practice of issuing traffic to the helicopters over the bridge so I informed aircraft X that I had issued the traffic.once aircraft Y landed; he asked about the flight of three helicopters off his right. I informed him I had issued traffic to aircraft X.neither aircraft declared a near miss on frequency. At all times I had maintained tower applied visual separation between aircraft X and aircraft Y.I recommend recurrent helicopter training for the facility to prevent this incident from occurring in the future with other controllers.
Original NASA ASRS Text
Title: DCA Controller reported they failed to issue traffic information to multiple VFR flights on approach.
Narrative: I was working the Local and Helicopter positions combined at DCA ATC. I have been CPC/FPL for [a short time].I accepted a handoff from Potomac TRACON on Aircraft X 2 miles west of ZZZ. Aircraft X contacted DCA Tower and requested to fly Route 1-Route 4 -ZZZ1 and then to ZZZ2. I radar contacted Aircraft X; approved the request and issued the altimeter.Aircraft Y called on a seven mile final to DCA and requested to land on Runway XX. I then I cleared Aircraft Y to land.Note. My standard practice for helicopters flying the DCA helicopter route is to issue any pertinent landing traffic by the time the helicopters pass over the South Capitol Street Bridge.Aircraft X asked if I had issued traffic on the aircraft landing Runway XX. I thought I had applied my standard practice of issuing traffic to the helicopters over the bridge so I informed Aircraft X that I had issued the traffic.Once Aircraft Y landed; he asked about the flight of three helicopters off his right. I informed him I had issued traffic to Aircraft X.Neither aircraft declared a near miss on frequency. At all times I had maintained Tower applied visual separation between Aircraft X and Aircraft Y.I recommend recurrent helicopter training for the facility to prevent this incident from occurring in the future with other controllers.
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.