37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 420214 |
Time | |
Date | 199811 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : bdr airport : bdr |
State Reference | CT |
Altitude | msl bound lower : 1000 msl bound upper : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bdr |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
Flight Phase | landing other |
Route In Use | approach : visual |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | other other : other pilot : commercial pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 35 flight time total : 3000 flight time type : 500 |
ASRS Report | 420214 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
In closed traffic for runway 29, on upwind, requested closed traffic for runway 24. Approved by ATC. On base for runway 24, advised ATC. ATC questioned what runway we were planning to touch- and-go if not runway 29. Controller appeared to be doing all 3 position (local, ground, and clearance) because we could hear him on ground, clearance and local (all on tower frequency). Additionally, he was having to rewrite at least 2 IFR clrncs because he was telling the IFR departures that he had to rewrite clrncs. Rewriting IFR clrncs is a common requirement for ATC at this tower. IFR arrs were using both runway 5 and runway 24. Our base for runway 24 could have been a safety issue if we were not keeping track of the IFR arrs. This controller does a good job with traffic, but when he has to do clearance, ground, local -- and rewrite clrncs as well as handle the approach landline -- we have a safety issue that needs to be addressed immediately. This is a common occurrence at bdr.
Original NASA ASRS Text
Title: PA28 PLT ADVISES THAT SINGLE CTLR IS DISTR BY WORKING 3 POS AT BDR.
Narrative: IN CLOSED TFC FOR RWY 29, ON UPWIND, REQUESTED CLOSED TFC FOR RWY 24. APPROVED BY ATC. ON BASE FOR RWY 24, ADVISED ATC. ATC QUESTIONED WHAT RWY WE WERE PLANNING TO TOUCH- AND-GO IF NOT RWY 29. CTLR APPEARED TO BE DOING ALL 3 POS (LCL, GND, AND CLRNC) BECAUSE WE COULD HEAR HIM ON GND, CLRNC AND LCL (ALL ON TWR FREQ). ADDITIONALLY, HE WAS HAVING TO REWRITE AT LEAST 2 IFR CLRNCS BECAUSE HE WAS TELLING THE IFR DEPS THAT HE HAD TO REWRITE CLRNCS. REWRITING IFR CLRNCS IS A COMMON REQUIREMENT FOR ATC AT THIS TWR. IFR ARRS WERE USING BOTH RWY 5 AND RWY 24. OUR BASE FOR RWY 24 COULD HAVE BEEN A SAFETY ISSUE IF WE WERE NOT KEEPING TRACK OF THE IFR ARRS. THIS CTLR DOES A GOOD JOB WITH TFC, BUT WHEN HE HAS TO DO CLRNC, GND, LCL -- AND REWRITE CLRNCS AS WELL AS HANDLE THE APCH LANDLINE -- WE HAVE A SAFETY ISSUE THAT NEEDS TO BE ADDRESSED IMMEDIATELY. THIS IS A COMMON OCCURRENCE AT BDR.
Data retrieved from NASA's ASRS site as of July 2007 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.