Narrative:

This flight plan had a field report that was almost a day old. Also, it was inaccurate with little mention of ramp construction and ATIS OTS. Only ATIS is departure ATIS. I called dispatch for a new report before takeoff. I informed agents of this when I arrived at hpn and next morning information still not current. As per recent atpac meeting field reports must be accurate to inform crew of 'left' type NOTAMS. Callback conversation with reporter revealed the following information: since the part 139 mandated responsibility of the operator to check all NOTAMS, the airlines have not been consistent in how they are able to get this information, what information they do get, or even the accuracy of the information received. This reporter's airline utilizes information emanated by the station's field report. This critical information is passed along sometimes by a non pilot type individual to another individual in an airline's operation who may also be a non pilot type, and this leaves a lot of room for communication errors. (Reporter has experienced 'packed ice' runway conditions when the report that he received stated 'wet.') reporter feels that since the FAA has mandated that NOTAM information is the operator's responsibility, that the FAA should also create a system that is easily accessible. The recent atpac recommendation to drop excessive information from the airport's ATIS has now created an even greater problem for the operator's ability to access information that is local in nature. If the operator is gathering information from the FSS report, then it is also often coming from a source that is not local and well familiarized with the current field conditions.

Google
 

Original NASA ASRS Text

Title: A ACR FK10 CAPT RPTS RECEIVING AN OLD FIELD RPT WHICH WAS NOT ONLY INACCURATE, BUT ALSO CONTAINED MINIMAL INFO REGARDING RAMP CONSTRUCTION. THE RPTR CITED CONCERNS ABOUT LEGAL PLT BRIEFING REQUIREMENTS OF HIS AIRLINE (PRIMARILY 'L' NOTAMS) VERSUS THE EASY ACCESSIBILITY OF THE INFO REQUIRED TO BE PRESENTED TO THE PLTS.

Narrative: THIS FLT PLAN HAD A FIELD RPT THAT WAS ALMOST A DAY OLD. ALSO, IT WAS INACCURATE WITH LITTLE MENTION OF RAMP CONSTRUCTION AND ATIS OTS. ONLY ATIS IS DEP ATIS. I CALLED DISPATCH FOR A NEW RPT BEFORE TKOF. I INFORMED AGENTS OF THIS WHEN I ARRIVED AT HPN AND NEXT MORNING INFO STILL NOT CURRENT. AS PER RECENT ATPAC MEETING FIELD RPTS MUST BE ACCURATE TO INFORM CREW OF 'L' TYPE NOTAMS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: SINCE THE PART 139 MANDATED RESPONSIBILITY OF THE OPERATOR TO CHK ALL NOTAMS, THE AIRLINES HAVE NOT BEEN CONSISTENT IN HOW THEY ARE ABLE TO GET THIS INFO, WHAT INFO THEY DO GET, OR EVEN THE ACCURACY OF THE INFO RECEIVED. THIS RPTR'S AIRLINE UTILIZES INFO EMANATED BY THE STATION'S FIELD RPT. THIS CRITICAL INFO IS PASSED ALONG SOMETIMES BY A NON PLT TYPE INDIVIDUAL TO ANOTHER INDIVIDUAL IN AN AIRLINE'S OP WHO MAY ALSO BE A NON PLT TYPE, AND THIS LEAVES A LOT OF ROOM FOR COM ERRORS. (RPTR HAS EXPERIENCED 'PACKED ICE' RWY CONDITIONS WHEN THE RPT THAT HE RECEIVED STATED 'WET.') RPTR FEELS THAT SINCE THE FAA HAS MANDATED THAT NOTAM INFO IS THE OPERATOR'S RESPONSIBILITY, THAT THE FAA SHOULD ALSO CREATE A SYS THAT IS EASILY ACCESSIBLE. THE RECENT ATPAC RECOMMENDATION TO DROP EXCESSIVE INFO FROM THE ARPT'S ATIS HAS NOW CREATED AN EVEN GREATER PROB FOR THE OPERATOR'S ABILITY TO ACCESS INFO THAT IS LCL IN NATURE. IF THE OPERATOR IS GATHERING INFO FROM THE FSS RPT, THEN IT IS ALSO OFTEN COMING FROM A SOURCE THAT IS NOT LCL AND WELL FAMILIARIZED WITH THE CURRENT FIELD CONDITIONS.

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.