 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Phx tower controller reported that the facility received a PIREP for severe rime icing; 80 minutes after it was reported. Reporter complained that it took too long to obtain the information.
| Attributes | |
| ACN | 1414299 |
| Time | |
| Date | 201701 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHX.Airport |
| State Reference | AZ |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
While working clearance delivery; I received an urgent PIREP via flight data input/output general information (fdio gi) message stating: urgent PIREP...dro XA30Z 140 BE40 sev rime icing... This was especially important to me to have this information since we have several flights daily going to durango; co. My technique would to be not only make a blanket transmission about the PIREP; but also specifically address flights going to that location to advise them and make sure they received the information. The issue is the PIREP was reported at XA30Z. I did not receive this urgent PIREP until XB50Z. Severe icing can cause an aircraft incident or accident in a matter of moments. It is unacceptable that it takes one hour and twenty minutes to disseminate this information. Better PIREP sharing system. Pireps should be entered in aisr [aeronautical information system replacement] immediately after receiving the report and should automatically be disseminated to facilities within a specified radius without having to be manually entered again by a traffic management unit; weather contractor; etc.
Original NASA ASRS Text
Title: PHX Tower Controller reported that the facility received a PIREP for Severe Rime Icing; 80 minutes after it was reported. Reporter complained that it took too long to obtain the information.
Narrative: While working Clearance Delivery; I received an Urgent PIREP via Flight Data Input/Output General Information (FDIO GI) message stating: URGENT PIREP...DRO XA30Z 140 BE40 SEV RIME ICING... This was especially important to me to have this information since we have several flights daily going to Durango; CO. My technique would to be not only make a blanket transmission about the PIREP; but also specifically address flights going to that location to advise them and make sure they received the information. The issue is the PIREP was reported at XA30Z. I did not receive this URGENT PIREP until XB50Z. Severe icing can cause an aircraft incident or accident in a matter of moments. It is unacceptable that it takes one hour and twenty minutes to disseminate this information. Better PIREP sharing system. PIREPs should be entered in AISR [Aeronautical Information System Replacement] immediately after receiving the report and should automatically be disseminated to facilities within a specified radius without having to be manually entered again by a Traffic Management Unit; Weather contractor; etc.
Data retrieved from NASA's ASRS site 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.