 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of BE20, failed to know the correct CTAF (unicom) frequency for a destination airport until advised on the published frequency by FBO of a change to new frequency. Reporter had been given latest NOTAMS by FAA FSS prior to takeoff, but no mention of frequency change was made.
| Attributes | |
| ACN | 391660 |
| Time | |
| Date | 199712 |
| Day | Wed |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : dnl |
| State Reference | GA |
| Altitude | msl bound lower : 2000 msl bound upper : 2000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : ags |
| Operator | general aviation : corporate |
| Make Model Name | Super King Air 200/Huron |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach descent other |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : atp |
| ASRS Report | 391660 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other other : unspecified |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | Pilot Deviation other |
| Situations | |
| Publication | Unspecified |
Narrative:
I was on an IFR flight plan from clt to dnl. I received NOTAMS on dnl from my duats briefing and from rdo FSS before takeoff. The only NOTAM mentioned was runway lights inoperative on runway 11/29. On arriving in the dnl area, I was in contact with ags approach control. WX was VFR and when we had dnl airport in sight, ags approach cleared us to contact dnl on the CTAF frequency. We went over to 122.8 (the published frequency) and after several xmissions were told by the FBO personnel that the CTAF was now 123.05. We changed to 123.05, did the appropriate calls and landed uneventfully. In light of the accident at quincy, il, and other collisions at non twred airports, I feel this information (frequency CTAF change) should be a 'D' NOTAM. It was not available in this case from rdu FSS. Also ags approach could have helped us by giving us the change, but did not. We need the correct CTAF, the system failed.
Original NASA ASRS Text
Title: PLT OF BE20, FAILED TO KNOW THE CORRECT CTAF (UNICOM) FREQ FOR A DEST ARPT UNTIL ADVISED ON THE PUBLISHED FREQ BY FBO OF A CHANGE TO NEW FREQ. RPTR HAD BEEN GIVEN LATEST NOTAMS BY FAA FSS PRIOR TO TKOF, BUT NO MENTION OF FREQ CHANGE WAS MADE.
Narrative: I WAS ON AN IFR FLT PLAN FROM CLT TO DNL. I RECEIVED NOTAMS ON DNL FROM MY DUATS BRIEFING AND FROM RDO FSS BEFORE TKOF. THE ONLY NOTAM MENTIONED WAS RWY LIGHTS INOP ON RWY 11/29. ON ARRIVING IN THE DNL AREA, I WAS IN CONTACT WITH AGS APCH CTL. WX WAS VFR AND WHEN WE HAD DNL ARPT IN SIGHT, AGS APCH CLRED US TO CONTACT DNL ON THE CTAF FREQ. WE WENT OVER TO 122.8 (THE PUBLISHED FREQ) AND AFTER SEVERAL XMISSIONS WERE TOLD BY THE FBO PERSONNEL THAT THE CTAF WAS NOW 123.05. WE CHANGED TO 123.05, DID THE APPROPRIATE CALLS AND LANDED UNEVENTFULLY. IN LIGHT OF THE ACCIDENT AT QUINCY, IL, AND OTHER COLLISIONS AT NON TWRED ARPTS, I FEEL THIS INFO (FREQ CTAF CHANGE) SHOULD BE A 'D' NOTAM. IT WAS NOT AVAILABLE IN THIS CASE FROM RDU FSS. ALSO AGS APCH COULD HAVE HELPED US BY GIVING US THE CHANGE, BUT DID NOT. WE NEED THE CORRECT CTAF, THE SYS FAILED.
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.