![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 168756 |
| Time | |
| Date | 199101 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : psc |
| State Reference | WA |
| Aircraft 1 | |
| Controlling Facilities | tower : dvt |
| Person 1 | |
| Affiliation | government : faa |
| Function | oversight : coordinator |
| Qualification | controller : radar |
| Experience | controller non radar : 1 controller radar : 6 |
| ASRS Report | 168756 |
| Person 2 | |
| Affiliation | government : faa |
| Function | oversight : coordinator |
| Qualification | controller : radar |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other other : unspecified atc |
| Resolutory Action | other |
| Consequence | faa : investigated |
| Supplementary | |
| Air Traffic Incident | other |
Narrative:
I was asked to take a data position and I asked if I could take the scope to get the picture. Due to cenrap problems I couldn't get a proper briefing, also the traffic load was so heavy I couldn't really grasp the whole situation. The data controller wanted me to jump in data and in turn she would take the scope. I couldn't do that under these conditions because I didn't want an operational error or deviation. Most errors occur at relief time and the controllers were only on for 25 mins and an hour and a half. I was suppose to be a savior and bail the controller out. Traffic distraction and my judgement precluded not to take the scope. Now I am facing disciplinary action due to this event. The real problem is cenrap doesn't work. The ASR-9 doesn't work and management expects us to work under these conditions with no exception. I feel safety is the biggest issue and management does also, but with ongoing personal conflicts between management/controllers, any action taken against a controller has precedent over any of the real problems. We as a whole are perceived as whiners and complainers. I will not take a position when both positions are out of control with numerous requirement problems. I felt I had to jump onto a burning ship and provide a rescue mission.
Original NASA ASRS Text
Title: CTLR REFUSED TO POSITION RELIEF.
Narrative: I WAS ASKED TO TAKE A DATA POS AND I ASKED IF I COULD TAKE THE SCOPE TO GET THE PICTURE. DUE TO CENRAP PROBS I COULDN'T GET A PROPER BRIEFING, ALSO THE TFC LOAD WAS SO HVY I COULDN'T REALLY GRASP THE WHOLE SITUATION. THE DATA CTLR WANTED ME TO JUMP IN DATA AND IN TURN SHE WOULD TAKE THE SCOPE. I COULDN'T DO THAT UNDER THESE CONDITIONS BECAUSE I DIDN'T WANT AN OPERATIONAL ERROR OR DEV. MOST ERRORS OCCUR AT RELIEF TIME AND THE CTLRS WERE ONLY ON FOR 25 MINS AND AN HR AND A HALF. I WAS SUPPOSE TO BE A SAVIOR AND BAIL THE CTLR OUT. TFC DISTR AND MY JUDGEMENT PRECLUDED NOT TO TAKE THE SCOPE. NOW I AM FACING DISCIPLINARY ACTION DUE TO THIS EVENT. THE REAL PROB IS CENRAP DOESN'T WORK. THE ASR-9 DOESN'T WORK AND MGMNT EXPECTS US TO WORK UNDER THESE CONDITIONS WITH NO EXCEPTION. I FEEL SAFETY IS THE BIGGEST ISSUE AND MGMNT DOES ALSO, BUT WITH ONGOING PERSONAL CONFLICTS BTWN MGMNT/CTLRS, ANY ACTION TAKEN AGAINST A CTLR HAS PRECEDENT OVER ANY OF THE REAL PROBS. WE AS A WHOLE ARE PERCEIVED AS WHINERS AND COMPLAINERS. I WILL NOT TAKE A POS WHEN BOTH POSITIONS ARE OUT OF CTL WITH NUMEROUS REQUIREMENT PROBS. I FELT I HAD TO JUMP ONTO A BURNING SHIP AND PROVIDE A RESCUE MISSION.
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.