37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 448089 |
Time | |
Date | 199909 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mvy.airport |
State Reference | MA |
Altitude | msl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : k90.tracon |
Operator | general aviation : personal |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Navigation In Use | other vortac |
Flight Phase | cruise : level |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : atp pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 50 flight time total : 2400 flight time type : 900 |
ASRS Report | 448089 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | FAA ATC Human Performance ATC Facility |
Primary Problem | FAA |
Narrative:
En route IFR from hya to mvy (in visual conditions) I checked in with approach on 118.2 as advised by hya tower. Made contact with cape approach, told them I had mvy ATIS. I was told to proceed direct to mvy. Cape then advised contact cape approach on 124.7. I checked in on 124.7 with cape. They acknowledged, then no further xmissions. As I approached about 7 NM from mvy, I was unable to raise cape on 124.7, so I called mvy tower on 121.4, advised them I lost contact with cape on 124.7, and I was IFR inbound. They said try cape on 133.75, which I did. I said unable on 124.7. Controller said he 'lost his position' or something like that. Cape told me to contact mvy tower, which I did, and landed safely. No idea what the problem at cape approach is. I wanted to make mvy tower aware I was inbound since there were other aircraft in the class D airspace. I have no idea if they had the IFR strip on me as an inbound, so I take nothing for granted.
Original NASA ASRS Text
Title: A PA28-181 CFI ENCOUNTERS RADAR COVERAGE PROBS WHILE ENRTE FROM HYA TO MVY, MA.
Narrative: ENRTE IFR FROM HYA TO MVY (IN VISUAL CONDITIONS) I CHKED IN WITH APCH ON 118.2 AS ADVISED BY HYA TWR. MADE CONTACT WITH CAPE APCH, TOLD THEM I HAD MVY ATIS. I WAS TOLD TO PROCEED DIRECT TO MVY. CAPE THEN ADVISED CONTACT CAPE APCH ON 124.7. I CHKED IN ON 124.7 WITH CAPE. THEY ACKNOWLEDGED, THEN NO FURTHER XMISSIONS. AS I APCHED ABOUT 7 NM FROM MVY, I WAS UNABLE TO RAISE CAPE ON 124.7, SO I CALLED MVY TWR ON 121.4, ADVISED THEM I LOST CONTACT WITH CAPE ON 124.7, AND I WAS IFR INBOUND. THEY SAID TRY CAPE ON 133.75, WHICH I DID. I SAID UNABLE ON 124.7. CTLR SAID HE 'LOST HIS POS' OR SOMETHING LIKE THAT. CAPE TOLD ME TO CONTACT MVY TWR, WHICH I DID, AND LANDED SAFELY. NO IDEA WHAT THE PROB AT CAPE APCH IS. I WANTED TO MAKE MVY TWR AWARE I WAS INBOUND SINCE THERE WERE OTHER ACFT IN THE CLASS D AIRSPACE. I HAVE NO IDEA IF THEY HAD THE IFR STRIP ON ME AS AN INBOUND, SO I TAKE NOTHING FOR GRANTED.
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.