 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A dispatcher's report regarding the failure of his office to inform flts under their jurisdiction of SIGMET. One flight descended early to FL290, into the altitudes contained in the SIGMET, FL220 to FL300.
| Attributes | |
| ACN | 400680 |
| Time | |
| Date | 199804 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : jfk |
| State Reference | NY |
| Altitude | msl bound lower : 29000 msl bound upper : 33000 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny |
| Operator | common carrier : air carrier |
| Make Model Name | B737-200 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | cruise other descent other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | other personnel other personnel other |
| Qualification | other |
| ASRS Report | 400680 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | inflight encounter other non adherence : far non adherence other other anomaly other |
| Independent Detector | other other : unspecified |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Chart Or Publication |
| Air Traffic Incident | other |
Narrative:
Flight departed rsw XD04 UTC and SIGMET for moderate-severe turbulence between FL220-FL300 in the vicinity of jfk-pvd-ack. Flight was planned at FL330 but never received SIGMET. I came on duty at XA30 UTC and during the turnover briefing SIGMET was never mentioned nor was it available to see. The flight reported moderate-severe turbulence at approximately XF28Z while descending early from cruise. I checked PIREPS and could not locate any moderate or severe reports in the area. It was not until approximately XH45Z when the SIGMET was canceled did I become aware the SIGMET had existed. It was at this time I researched the history and found the SIGMET and discovered this flight and other flts had not received this information.
Original NASA ASRS Text
Title: A DISPATCHER'S RPT REGARDING THE FAILURE OF HIS OFFICE TO INFORM FLTS UNDER THEIR JURISDICTION OF SIGMET. ONE FLT DSNDED EARLY TO FL290, INTO THE ALTS CONTAINED IN THE SIGMET, FL220 TO FL300.
Narrative: FLT DEPARTED RSW XD04 UTC AND SIGMET FOR MODERATE-SEVERE TURB BTWN FL220-FL300 IN THE VICINITY OF JFK-PVD-ACK. FLT WAS PLANNED AT FL330 BUT NEVER RECEIVED SIGMET. I CAME ON DUTY AT XA30 UTC AND DURING THE TURNOVER BRIEFING SIGMET WAS NEVER MENTIONED NOR WAS IT AVAILABLE TO SEE. THE FLT RPTED MODERATE-SEVERE TURB AT APPROX XF28Z WHILE DSNDING EARLY FROM CRUISE. I CHKED PIREPS AND COULD NOT LOCATE ANY MODERATE OR SEVERE RPTS IN THE AREA. IT WAS NOT UNTIL APPROX XH45Z WHEN THE SIGMET WAS CANCELED DID I BECOME AWARE THE SIGMET HAD EXISTED. IT WAS AT THIS TIME I RESEARCHED THE HISTORY AND FOUND THE SIGMET AND DISCOVERED THIS FLT AND OTHER FLTS HAD NOT RECEIVED THIS INFO.
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.