Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
For destination filing we can use the area forecast if it is VFR, if it is marginal we purchase a custom forecast from Jepps for that airport. We can never use another airports wx, except altimeter when so noted on the approach plate.
METAR not required by reg.
121.613
reports "or" forecast
Now at the old, old carrier (my first place) we couldn't leave either. If the temp, altimeter and even visibility was missing we needed to have an on site weather observer or the flight got delayed, or canceled. This was quite common flying to small airports in North Dakota and the UP of Michigan and what not.I just don't understand why their can't be a universal exception to the temp or altimeter setting being missing. I don't know if I have ever seen a significant difference in altimeter or temperature settings between airports that were within a relatively short distance of each other. It's frustrating to take a delay on a flight for something like this. Seems like different rules and exceptions apply depending on your FSDO, even though we are all 121 carriers.
Now will the reliability of the Asos at BFE be any better?
From what I understand, the new OpSpecs A010 that comes out soon is going to mandate that there can be no missing elements from any automated report.
Now will the reliability of the Asos at BFE be any better? What are you smokin'