 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An MU20 private pilot performs an instrument departure procedure from O22 using the procedure as defined for the cuf NDB instrument departure procedure located at columbia, ca. After takeoff the pilot realizes that the signal is not available since, as later learned, the NDB was decommissioned or OTS.
| Attributes | |
| ACN | 424075 |
| Time | |
| Date | 199812 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : o22 |
| State Reference | CA |
| Altitude | agl bound lower : 500 agl bound upper : 800 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | M-20 Scotsman |
| Flight Phase | climbout : initial |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument |
| Experience | flight time last 90 days : 25 flight time total : 800 flight time type : 10 |
| ASRS Report | 424075 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Events | |
| Anomaly | non adherence : clearance non adherence : far non adherence other other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I had flown VFR from pao to O22 and had intended to return VFR. Clouds moved in and I checked my charts and they showed an IFR departure based on the cuf NDB. I called ZOA and requested an IFR clearance to VFR on top. It was granted. Then I couldn't find cuf on either my en route charts or plates. I finally located the frequency (404) in my GPS and dialed it in -- no response. But I figured it was just the location and I would pick it up soon. The departure procedure is straight out. I climbed into the clouds and came back out and then canceled my clearance with ZOA. IMC was so short that I never consulted my NDB. Upon returning home, I found an fdc NOTAM that the departure procedure had been canceled, probably because the NDB is either OTS or decommissioned. I still don't know. FSS didn't know either as of jan/xa/99. Bottom line: check and rechk NOTAMS.
Original NASA ASRS Text
Title: AN MU20 PVT PLT PERFORMS AN INST DEP PROC FROM O22 USING THE PROC AS DEFINED FOR THE CUF NDB INST DEP PROC LOCATED AT COLUMBIA, CA. AFTER TKOF THE PLT REALIZES THAT THE SIGNAL IS NOT AVAILABLE SINCE, AS LATER LEARNED, THE NDB WAS DECOMMISSIONED OR OTS.
Narrative: I HAD FLOWN VFR FROM PAO TO O22 AND HAD INTENDED TO RETURN VFR. CLOUDS MOVED IN AND I CHKED MY CHARTS AND THEY SHOWED AN IFR DEP BASED ON THE CUF NDB. I CALLED ZOA AND REQUESTED AN IFR CLRNC TO VFR ON TOP. IT WAS GRANTED. THEN I COULDN'T FIND CUF ON EITHER MY ENRTE CHARTS OR PLATES. I FINALLY LOCATED THE FREQ (404) IN MY GPS AND DIALED IT IN -- NO RESPONSE. BUT I FIGURED IT WAS JUST THE LOCATION AND I WOULD PICK IT UP SOON. THE DEP PROC IS STRAIGHT OUT. I CLBED INTO THE CLOUDS AND CAME BACK OUT AND THEN CANCELED MY CLRNC WITH ZOA. IMC WAS SO SHORT THAT I NEVER CONSULTED MY NDB. UPON RETURNING HOME, I FOUND AN FDC NOTAM THAT THE DEP PROC HAD BEEN CANCELED, PROBABLY BECAUSE THE NDB IS EITHER OTS OR DECOMMISSIONED. I STILL DON'T KNOW. FSS DIDN'T KNOW EITHER AS OF JAN/XA/99. BOTTOM LINE: CHK AND RECHK NOTAMS.
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.