37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 737922 |
Time | |
Date | 200705 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : zfw.artcc |
State Reference | TX |
Altitude | msl bound lower : 0 msl bound upper : 23000 |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 19.3 controller time certified in position1 : 18 |
ASRS Report | 737922 |
Events | |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | FAA |
Primary Problem | FAA |
Situations | |
ATC Facility | procedure or policy : zfw.artcc |
Narrative:
I recently reported that management rescinded the directive to 7110.65 5-14-3 (see 7210.3 8-2-7). Those reports centered on the increase in complexity in both the low and high sectors (enter then remove the temperature altitude). On may/xa/07; management further complicated matters by adding automation which; upon handoff from D10 to ZFW; a temperature 170 is entered into the data block for all jets. Their rationale: now the data block 'really' complies with 5-14-3(B). From an operational standpoint; this only makes the sector more difficult as more time is now going to be looking away from the radar. Tonight; I worked uim-lo (83). I found myself making more flight plan readout requests or looking to the uret more often to determine information which had been readily available; and therefore taking my attention away from the radar. And again; with WX impacting our airspace; both uim-lo (83) and txk-hi (90) did not need the additional workload created by the requirement to remove temperature 170; enter temperature 230; then remove temperature 230 again. In an effort to 'fix a problem' which never existed; management has created a situation which has tripled workload; has already been somewhat causal in 1 error; still only applies to 1 of 4 departure gates; and will lead to another error (or perhaps worse).
Original NASA ASRS Text
Title: ZFW CTLR VOICED CONCERN REGARDING FAC MGMNT'S DECISION TO IMPLEMENT NEW PROCS THAT ALLEGEDLY INCREASE WORKLOAD.
Narrative: I RECENTLY RPTED THAT MGMNT RESCINDED THE DIRECTIVE TO 7110.65 5-14-3 (SEE 7210.3 8-2-7). THOSE RPTS CTRED ON THE INCREASE IN COMPLEXITY IN BOTH THE LOW AND HIGH SECTORS (ENTER THEN REMOVE THE TEMP ALT). ON MAY/XA/07; MGMNT FURTHER COMPLICATED MATTERS BY ADDING AUTOMATION WHICH; UPON HDOF FROM D10 TO ZFW; A TEMP 170 IS ENTERED INTO THE DATA BLOCK FOR ALL JETS. THEIR RATIONALE: NOW THE DATA BLOCK 'REALLY' COMPLIES WITH 5-14-3(B). FROM AN OPERATIONAL STANDPOINT; THIS ONLY MAKES THE SECTOR MORE DIFFICULT AS MORE TIME IS NOW GOING TO BE LOOKING AWAY FROM THE RADAR. TONIGHT; I WORKED UIM-LO (83). I FOUND MYSELF MAKING MORE FLT PLAN READOUT REQUESTS OR LOOKING TO THE URET MORE OFTEN TO DETERMINE INFO WHICH HAD BEEN READILY AVAILABLE; AND THEREFORE TAKING MY ATTN AWAY FROM THE RADAR. AND AGAIN; WITH WX IMPACTING OUR AIRSPACE; BOTH UIM-LO (83) AND TXK-HI (90) DID NOT NEED THE ADDITIONAL WORKLOAD CREATED BY THE REQUIREMENT TO REMOVE TEMP 170; ENTER TEMP 230; THEN REMOVE TEMP 230 AGAIN. IN AN EFFORT TO 'FIX A PROB' WHICH NEVER EXISTED; MGMNT HAS CREATED A SITUATION WHICH HAS TRIPLED WORKLOAD; HAS ALREADY BEEN SOMEWHAT CAUSAL IN 1 ERROR; STILL ONLY APPLIES TO 1 OF 4 DEP GATES; AND WILL LEAD TO ANOTHER ERROR (OR PERHAPS WORSE).
Data retrieved from NASA's ASRS site as of January 2009 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.