37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 911010 |
Time | |
Date | 201009 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | HYA.Airport |
State Reference | MA |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Radar 24 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Hya fct launched a single engine aircraft going to mvy off runway 24 on a 270 heading. I called hya fct and asked to turn the aircraft back toward mvy as the heading would put the aircraft in conflict with traffic at fmh unless he was given a climb. Hya advised 'no you can't turn him I have a jet departing shortly going over sey' which the tower controller must have thought to be a 240 heading. For some reason the tower controller ignored the fact that the first fix was cossy which is approximately a 270 heading. Normally departures are assigned a heading that will enable the radar controller to expedite the individual departure on course. I advised the tower controller he may want to call before over to the departure controller before getting 'too creative' with vectors. Controller seemed to take offense to this and made some snide comment about using radar. This is not the first time we have had a problem with hya fct using headings for departures that create problems of various degrees for pilots and controllers. In a recent event hya fct turned both IFR and VFR departures toward a tfr over fmh. Only the quick reaction of the departure controller kept the aircraft away from the tfr. I continue to recommend either limiting hya fct to one heading for each runway; allowing the radar controller to take immediate control of departures; or K90 designing a training syllabus for hya fct as they do not have one in place.
Original NASA ASRS Text
Title: A K90 Controller discussed HYA Tower Controller procedures which allow HYA departing aircraft to depart on headings that put them in conflict with a TFR; nearby airports; and other traffic.
Narrative: HYA FCT launched a single engine aircraft going to MVY off Runway 24 on a 270 heading. I called HYA FCT and asked to turn the aircraft back toward MVY as the heading would put the aircraft in conflict with traffic at FMH unless he was given a climb. HYA advised 'no you can't turn him I have a jet departing shortly going over SEY' which the tower Controller must have thought to be a 240 heading. For some reason the Tower Controller ignored the fact that the first fix was COSSY which is approximately a 270 heading. Normally departures are assigned a heading that will enable the Radar Controller to expedite the individual departure on course. I advised the Tower Controller he may want to call before over to the Departure Controller before getting 'too creative' with vectors. Controller seemed to take offense to this and made some snide comment about using RADAR. This is not the first time we have had a problem with HYA FCT using headings for departures that create problems of various degrees for pilots and controllers. In a recent event HYA FCT turned both IFR and VFR departures toward a TFR over FMH. Only the quick reaction of the Departure Controller kept the aircraft away from the TFR. I continue to recommend either limiting HYA FCT to one heading for each runway; allowing the RADAR Controller to take immediate control of departures; or K90 designing a training syllabus for HYA FCT as they do not have one in place.
Data retrieved from NASA's ASRS site as of April 2012 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.