37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 779495 |
Time | |
Date | 200803 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : msp.airport |
State Reference | MN |
Altitude | msl single value : 2700 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : msp.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : on vectors |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 5 flight time total : 14000 flight time type : 100 |
ASRS Report | 779495 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | FAA |
Primary Problem | FAA |
Narrative:
Attempted to contact minneapolis approach control on published frequency of 125.0. Attempt unsuccessful. Tried secondary frequency and was advised that new frequency was 134.7. Had received FSS standard weather briefing and no mention was made of this frequency change. Next day again got standard weather briefing and no mention was made of a NOTAM for this frequency change. Asked briefer if she saw any NOTAM for a frequency change for minneapolis approach control to 134.7 vice 125.0. She stated that she did see such a NOTAM in the 'distant' NOTAMS and didn't think that it was important to our flight. I did inform her that it was very important to flights arriving anywhere in the minneapolis south metropolitan area. Further internet investigation of this NOTAM reveals that it is published in NOTAMS for msp but not for any other satellite airport. In reality the NOTAM does not affect msp as the frequency is not used for msp traffic but is for aircraft arriving or departing from airports south of msp. Not showing this NOTAM for south satellite airports appears to be either a deficiency in the NOTAM system or a shortcoming on the part of the NOTAM filer in that it did not appear in the NOTAMS for the airports that were affected.
Original NASA ASRS Text
Title: C172 PILOT REPORTS THAT NOTAM FOR MSP APPROACH CONTROL FREQUENCY CHANGE DOES NOT APPEAR WITH ARPTS THAT ARE SERVED BY THIS SECTOR.
Narrative: ATTEMPTED TO CONTACT MINNEAPOLIS APPROACH CONTROL ON PUBLISHED FREQUENCY OF 125.0. ATTEMPT UNSUCCESSFUL. TRIED SECONDARY FREQUENCY AND WAS ADVISED THAT NEW FREQUENCY WAS 134.7. HAD RECEIVED FSS STANDARD WEATHER BRIEFING AND NO MENTION WAS MADE OF THIS FREQUENCY CHANGE. NEXT DAY AGAIN GOT STANDARD WEATHER BRIEFING AND NO MENTION WAS MADE OF A NOTAM FOR THIS FREQUENCY CHANGE. ASKED BRIEFER IF SHE SAW ANY NOTAM FOR A FREQUENCY CHANGE FOR MINNEAPOLIS APPROACH CONTROL TO 134.7 VICE 125.0. SHE STATED THAT SHE DID SEE SUCH A NOTAM IN THE 'DISTANT' NOTAMS AND DIDN'T THINK THAT IT WAS IMPORTANT TO OUR FLIGHT. I DID INFORM HER THAT IT WAS VERY IMPORTANT TO FLIGHTS ARRIVING ANYWHERE IN THE MINNEAPOLIS SOUTH METRO AREA. FURTHER INTERNET INVESTIGATION OF THIS NOTAM REVEALS THAT IT IS PUBLISHED IN NOTAMS FOR MSP BUT NOT FOR ANY OTHER SATELLITE AIRPORT. IN REALITY THE NOTAM DOES NOT AFFECT MSP AS THE FREQUENCY IS NOT USED FOR MSP TRAFFIC BUT IS FOR AIRCRAFT ARRIVING OR DEPARTING FROM AIRPORTS SOUTH OF MSP. NOT SHOWING THIS NOTAM FOR SOUTH SATELLITE AIRPORTS APPEARS TO BE EITHER A DEFICIENCY IN THE NOTAM SYSTEM OR A SHORTCOMING ON THE PART OF THE NOTAM FILER IN THAT IT DID NOT APPEAR IN THE NOTAMS FOR THE AIRPORTS THAT WERE AFFECTED.
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.