37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 814371 |
Time | |
Date | 200811 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : sea.airport |
State Reference | WA |
Altitude | msl single value : 3000 |
Environment | |
Flight Conditions | IMC |
Weather Elements | Fog |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : s46.tracon |
Operator | common carrier : air carrier |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 16l other |
Flight Phase | descent : approach landing : missed approach |
Route In Use | approach : instrument precision |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 128 flight time type : 2526 |
ASRS Report | 814371 |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | ATC Human Performance FAA |
Primary Problem | FAA |
Narrative:
Sea visibility 0 SM and vertical visibility 100 ft in fog. No RVR was given in ATIS. Simultaneous approaches to runways 16L and 16R were in use. Fdc NOTAM 7/2249: ILS runway 16L CAT ii and CAT III amdt 3B. Procedures na. Temporary crane 562 ft MSL 868 ft east of runway 16L/34R. (I have saved original fdc NOTAMS from this flight.) we briefed a CAT IIIB autoland to runway 16R and were later told by approach to 'expect runway 16R.' then after handoff to the next approach controller we were assigned runway 16L; just prior to turning base. I immediately asked for the RVR and was told 1800 ft. I then reprogrammed the box for a CAT I approach to runway 16L. The captain was PF and at DH did not have the runway environment in sight and we executed a missed approach. Approach asked if we would like vectors back to try it again. I stated we wanted vectors to runway 16R so we could conduct at CAT III approach. I also told them there was an fdc NOTAM prohibiting CAT ii and CAT III approaches to runway 16L. The controller appeared surprised by this information. While being vectored to runway 16R approach control asked for the number of the fdc NOTAM. I gave it to him. We successfully accomplished a CAT III autoland on runway 16R. At the completion of the flight; the captain called dispatch and they could not find that NOTAM -- I suspect approach control deleted it with the information I gave them. It was in the packet for our return flight but only because it was probably printed out as we were landing. I am filing this because we were aware of the NOTAM and therefore flew a CAT I. We saw (TCAS) and heard numerous flights making successful approaches and landings to runway 16L prior to us. Arrivals were being evenly split between both runways. It is obvious to me from the weather reported and observed that no one was able to land CAT I on runway 16L. I believe everyone was utilizing CAT ii or CAT III -- they just didn't read the fdc NOTAMS. I faithfully do and am penalized for it. The fdc NOTAM system is broken. Every listing is repeated at least twice and often four times; at every airport; which increases the amount of data I have to wade through every leg.
Original NASA ASRS Text
Title: AN A319 FIRST OFFICER COMPLAINED ABOUT FDC NOTAM PROCEDURES; NOTING LISTINGS ARE OFTEN OUT OF DATE AND REPEATED MULTIPLE TIMES; MAKING IT DIFFICULT TO EFFICIENTLY READ AND COMPLY WITH NOTAMS. ON THIS PARTICULAR FLIGHT THEY MISSED THE APPROACH AT SEA BECAUSE OF A NOTAM THAT WAS OUT OF DATE BUT INCLUDED IN THEIR PACKET.
Narrative: SEA VISIBILITY 0 SM AND VERTICAL VISIBILITY 100 FT IN FOG. NO RVR WAS GIVEN IN ATIS. SIMULTANEOUS APPROACHES TO RUNWAYS 16L AND 16R WERE IN USE. FDC NOTAM 7/2249: ILS RWY 16L CAT II AND CAT III AMDT 3B. PROCEDURES NA. TEMPORARY CRANE 562 FT MSL 868 FT EAST OF RWY 16L/34R. (I HAVE SAVED ORIGINAL FDC NOTAMS FROM THIS FLIGHT.) WE BRIEFED A CAT IIIB AUTOLAND TO RUNWAY 16R AND WERE LATER TOLD BY APPROACH TO 'EXPECT RUNWAY 16R.' THEN AFTER HANDOFF TO THE NEXT APPROACH CONTROLLER WE WERE ASSIGNED RUNWAY 16L; JUST PRIOR TO TURNING BASE. I IMMEDIATELY ASKED FOR THE RVR AND WAS TOLD 1800 FT. I THEN REPROGRAMMED THE BOX FOR A CAT I APPROACH TO RUNWAY 16L. THE CAPTAIN WAS PF AND AT DH DID NOT HAVE THE RUNWAY ENVIRONMENT IN SIGHT AND WE EXECUTED A MISSED APPROACH. APPROACH ASKED IF WE WOULD LIKE VECTORS BACK TO TRY IT AGAIN. I STATED WE WANTED VECTORS TO RUNWAY 16R SO WE COULD CONDUCT AT CAT III APPROACH. I ALSO TOLD THEM THERE WAS AN FDC NOTAM PROHIBITING CAT II AND CAT III APPROACHES TO RUNWAY 16L. THE CONTROLLER APPEARED SURPRISED BY THIS INFORMATION. WHILE BEING VECTORED TO RUNWAY 16R APPROACH CONTROL ASKED FOR THE NUMBER OF THE FDC NOTAM. I GAVE IT TO HIM. WE SUCCESSFULLY ACCOMPLISHED A CAT III AUTOLAND ON RUNWAY 16R. AT THE COMPLETION OF THE FLIGHT; THE CAPTAIN CALLED DISPATCH AND THEY COULD NOT FIND THAT NOTAM -- I SUSPECT APPROACH CONTROL DELETED IT WITH THE INFO I GAVE THEM. IT WAS IN THE PACKET FOR OUR RETURN FLIGHT BUT ONLY BECAUSE IT WAS PROBABLY PRINTED OUT AS WE WERE LANDING. I AM FILING THIS BECAUSE WE WERE AWARE OF THE NOTAM AND THEREFORE FLEW A CAT I. WE SAW (TCAS) AND HEARD NUMEROUS FLIGHTS MAKING SUCCESSFUL APPROACHES AND LANDINGS TO RUNWAY 16L PRIOR TO US. ARRIVALS WERE BEING EVENLY SPLIT BETWEEN BOTH RUNWAYS. IT IS OBVIOUS TO ME FROM THE WEATHER REPORTED AND OBSERVED THAT NO ONE WAS ABLE TO LAND CAT I ON RUNWAY 16L. I BELIEVE EVERYONE WAS UTILIZING CAT II OR CAT III -- THEY JUST DIDN'T READ THE FDC NOTAMS. I FAITHFULLY DO AND AM PENALIZED FOR IT. THE FDC NOTAM SYSTEM IS BROKEN. EVERY LISTING IS REPEATED AT LEAST TWICE AND OFTEN FOUR TIMES; AT EVERY AIRPORT; WHICH INCREASES THE AMOUNT OF DATA I HAVE TO WADE THROUGH EVERY LEG.
Data retrieved from NASA's ASRS site as of May 2009 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.