Fai controller described a departure event when aircraft was permitted to depart VFR with weather be...

Narrative:

Local control called tower visibility of 5 or maybe 7 miles and updated the ASOS prior to the hourly weather observation. I must have heard the ASOS beep as I thought the change had been accepted and the timing was correct for our typical hourly report (53-54 minutes after the hour). A carrier jet called for clearance and a PA31 called for a VFR TRSA departure and taxi. I issued the TRSA and taxi; and then issued the IFR clearance. After receiving a rolling call; the TRACON rang the tower phone to inquire about whether the field was VFR; at which point I noticed that the ASOS was still showing an IFR visibility and the pending hourly observation with a VFR visibility. This observation should have already been steadied as it was about 55 or 45 minutes after the hour. The TRSA departure was midfield airborne and the local controller was already taking action to fix the situation. I believe he offered an IFR clearance and the pilot requested and received an SVFR clearance. The clock on the ASOS was several minutes off from the tower's GPS clocks. The facility initially investigated this event as a possible operational error/operational deviation; but found it to be a non-event. Management is pursuing a correction to the ASOS clock.

Original NASA ASRS Text

Title: FAI controller described a departure event when aircraft was permitted to depart VFR with weather below basic VFR conditions; citing ASOS clock error as one causal factor.

Narrative: Local Control called Tower visibility of 5 or maybe 7 miles and updated the ASOS prior to the hourly weather observation. I must have heard the ASOS beep as I thought the change had been accepted and the timing was correct for our typical hourly report (53-54 minutes after the hour). A carrier jet called for clearance and a PA31 called for a VFR TRSA departure and taxi. I issued the TRSA and taxi; and then issued the IFR clearance. After receiving a rolling call; the TRACON rang the Tower phone to inquire about whether the field was VFR; at which point I noticed that the ASOS was still showing an IFR visibility and the pending hourly observation with a VFR visibility. This observation should have already been steadied as it was about 55 or 45 minutes after the hour. The TRSA departure was midfield airborne and the Local Controller was already taking action to fix the situation. I believe he offered an IFR clearance and the Pilot requested and received an SVFR clearance. The clock on the ASOS was several minutes off from the Tower's GPS clocks. The facility initially investigated this event as a possible operational error/operational deviation; but found it to be a non-event. Management is pursuing a correction to the ASOS clock.

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.

Attributes
ACN	823924
Time
Date	200902
Place
Locale Reference	FAI.Airport
State Reference	AK
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-31 Navajo/Chieftan/Mojave/T1040
Operating Under FAR Part	Part 135
Flight Phase	Takeoff
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Radar 8 Air Traffic Control Time Certified In Pos 1 (yrs) 7
Events
Anomaly	Deviation - Procedural Published Material / Policy

Fai controller described a departure event when aircraft was permitted to depart VFR with weather below basic VFR conditions; citing ASOS clock error as one causal factor.