HUF CTLR EXPRESSED FRUSTRATION REGARDING MAINT REFUSAL TO CONSIDER THE ILS LOC OTS BASED UPON MONITOR INDICATIONS; INSISTING ON A PIREP.
Synopsis
HUF CTLR EXPRESSED FRUSTRATION REGARDING MAINT REFUSAL TO CONSIDER THE ILS LOC OTS BASED UPON MONITOR INDICATIONS; INSISTING ON A PIREP.
Narrative
THE LOC AT HUF WENT INTO ALARM; INDICATING THAT IT WAS OTS. AFTER GIVING IT ENOUGH TIME TO RESET ITSELF; THE ALARM CONTINUED; SO WE CALLED MID-STATES MOCC TO RPT IT OTS. UPON RPTING IT TO THEM; WE WERE TOLD THAT THEY WOULD NOT CALL IT OTS UNTIL WE HAD A PIREP TO VERIFY IT. TFC WAS SLOW; SO THE LOC REMAINED IN ALARM FOR APPROX 7 HRS BEFORE WE COULD VERIFY IT WITH A PIREP. PER THE 7210.3; PARAGRAPH 3-5-1; A PIREP IS ONLY REQUIRED IF THE MONITOR EQUIP IS SUSPECT. I CAN NEVER RECALL THE LOC GOING INTO ALARM HERE WHEN IT WAS FOUND TO BE THE FAULT OF THE MONITORING EQUIP. PER THE 7210.3; PARAGRAPH 3-5-2B AND B4; I AM TO DISCONTINUE THE USE OF THIS EQUIP AND RPT IT OTS IF IT GOES INTO ALARM AND DOES NOT RESET ON ITS OWN. I FIND THIS LATEST INSTANCE OF THE FAA RUNNING AIR TFC ON THE BASIS OF A BUSINESS MODEL INSTEAD OF A SAFETY MODEL TO BE REPREHENSIBLE. SINCE THE MOCC WILL NOT CALL EQUIP OTS AND ISSUE THE APPROPRIATE NOTAM WHEN IT IS IN ALARM; THE NEXT TIME THIS HAPPENS; I WILL CALL FSS MYSELF (IF I CAN EVEN GET A HOLD OF THEM; BUT I DIGRESS...) AND ISSUE THE NOTAM. THE ONLY PROB WITH THIS PLAN OF ACTION IS THAT I CAN'T GO OUT AND ACTUALLY FIX THE LOC MYSELF. WE'LL STILL NEED A PIREP TO GET THE EQUIP BACK IN SVC; NO MATTER HOW MANY HRS THE RESTORATION MAY BE DELAYED. SINCE WHEN DOES A GOV AGENCY JUST GET TO MAKE UP THEIR OWN RULES AS THEY GO; SUPPOSEDLY TO SAVE A BUCK; AT THE EXPENSE OF SAFETY; IN DIRECT OPPOSITION TO A PUBLISHED ORDER?
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.