 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDV controller report a PIREP filed via the enroute information display system did not show up for 37 minutes.
| Attributes | |
| ACN | 1382526 |
| Time | |
| Date | 201608 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZDV.ARTCC |
| State Reference | CO |
| Environment | |
| Flight Conditions | Marginal |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
Flow control metering into den. Traffic management unit (tmu) informed they 'lost a runway' due to weather. Metering times increased by 4 or more minutes per aircraft. All aircraft were issued given headings and descents for delays. Aircraft X was descending to or just leveling at 19000 feet and reported moderate mixed ice and icing system failure with overheat. Aircraft X requested a lower altitude; no emergency declared. PIREP was reported at xa:33. As of xb:10 still no PIREP in erids (enroute information display system) on sector. I got off position and alerted tmu. On a related note; I didn't inform management only because there were no supervisors in the area; nor was there all day. The controller in charge knew; but I'm not sure they count as management; and I guess it didn't occur to me to tell the operations manager in charge.as of right now the PIREP via erids to tmu then back to erids system appears to not work well enough to be safe/timely. I recommend a return to paper PIREP forms that alert tmu to their presence via a controller walking down to tmu and handing it to them. Either that or some form of audible alert; perhaps; that goes off in tmu when a PIREP comes down. Thirty seven minutes of inactivity on a moderate icing PIREP that caused a system failure in a turbojet aircraft is unacceptable.
Original NASA ASRS Text
Title: ZDV Controller report a PIREP filed via the Enroute Information Display System did not show up for 37 minutes.
Narrative: Flow Control Metering into DEN. Traffic Management Unit (TMU) informed they 'lost a runway' due to weather. Metering times increased by 4 or more minutes per aircraft. All aircraft were issued given headings and descents for delays. Aircraft X was descending to or just leveling at 19000 feet and reported moderate mixed ice and icing system failure with overheat. Aircraft X requested a lower altitude; no emergency declared. PIREP was reported at XA:33. As of XB:10 still no PIREP in ERIDS (Enroute Information Display System) on sector. I got off position and alerted TMU. On a related note; I didn't inform management only because there were no supervisors in the area; nor was there all day. The Controller In Charge knew; but I'm not sure they count as management; and I guess it didn't occur to me to tell the Operations Manager In Charge.As of right now the PIREP via ERIDS to TMU then back to ERIDS system appears to not work well enough to be safe/timely. I recommend a return to paper PIREP forms that alert TMU to their presence via a controller walking down to TMU and handing it to them. Either that or some form of audible alert; perhaps; that goes off in TMU when a PIREP comes down. Thirty seven minutes of inactivity on a moderate icing PIREP that caused a system failure in a turbojet aircraft is unacceptable.
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.