37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 592177 |
Time | |
Date | 200308 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : msy.airport |
State Reference | LA |
Altitude | msl single value : 1200 |
Environment | |
Flight Conditions | VMC |
Weather Elements | Thunderstorm Windshear other |
Aircraft 1 | |
Controlling Facilities | tower : msy.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 592177 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | inflight encounter : weather non adherence : far non adherence : company policies non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : microburst, dappler radar other flight crewa other flight crewb |
Resolutory Action | none taken : anomaly accepted |
Consequence | other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Weather Company |
Primary Problem | Flight Crew Human Performance |
Narrative:
During approach to msy runway 10, approach control reported microburst alert on final for opposing runway 28. There was a cell just east of the runway. After switching to tower, they called a microburst alert for departure path runway 10, not for the arrival. Later, they reported other microburst alerts on other parts of the airport, north of the runway a few mi. The end result was I never understood there to be a microburst alert for our arrival path,. But I felt like there was a little too much information. Microburst reports were moving to different locations and the end result was I never understood there to be a microburst report for our runway, but by the time we landed, I wasn't so sure. The copilot felt sure there was not a microburst report for our runway. There was no warning from predictive windshear system and we had no variation in airspeed, smooth conditions and landed without incident.
Original NASA ASRS Text
Title: AN A320 CREW IGNORED MULTIPLE MICROBURST WARNINGS FROM THE ATCT LCL CTLR IN NON COMPLIANCE WITH COMPANY AND FOM REGS.
Narrative: DURING APCH TO MSY RWY 10, APCH CTL RPTED MICROBURST ALERT ON FINAL FOR OPPOSING RWY 28. THERE WAS A CELL JUST E OF THE RWY. AFTER SWITCHING TO TWR, THEY CALLED A MICROBURST ALERT FOR DEP PATH RWY 10, NOT FOR THE ARR. LATER, THEY RPTED OTHER MICROBURST ALERTS ON OTHER PARTS OF THE ARPT, N OF THE RWY A FEW MI. THE END RESULT WAS I NEVER UNDERSTOOD THERE TO BE A MICROBURST ALERT FOR OUR ARR PATH,. BUT I FELT LIKE THERE WAS A LITTLE TOO MUCH INFO. MICROBURST RPTS WERE MOVING TO DIFFERENT LOCATIONS AND THE END RESULT WAS I NEVER UNDERSTOOD THERE TO BE A MICROBURST RPT FOR OUR RWY, BUT BY THE TIME WE LANDED, I WASN'T SO SURE. THE COPLT FELT SURE THERE WAS NOT A MICROBURST RPT FOR OUR RWY. THERE WAS NO WARNING FROM PREDICTIVE WINDSHEAR SYS AND WE HAD NO VARIATION IN AIRSPD, SMOOTH CONDITIONS AND LANDED WITHOUT INCIDENT.
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.