37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1266764 |
Time | |
Date | 201505 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | UNV.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 20 Flight Crew Total 520 Flight Crew Type 300 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown |
Narrative:
I was on an IFR flight plan and was given a full route clearance; but after the first few legs I was cleared direct from talli intersection to my destination. I was speaking to new york [center] at the time of the incident. I did a radio check at about xa:50 to xa:55 am. Got a 'loud and clear' response from new york. At xb:08 I noticed that the controllers voice had changed and the transmissions had become somewhat fuzzy. I attempted to speak to the controller and received no response. At xb:10; after several attempts to raise the controller I contacted the tower at university park field on 128.7 and asked for the frequency of the next appropriate controller. I was given cleveland 124.4. I immediately checked in with cleveland; continued my flight and landed without incident. This is the second time this has happened to me on this route. The first time it happened a little further down the road when I was talking to mansfield. I feel pretty sure that in both cases that I did not receive a handoff. But I cannot be certain of that. It is possible that in one or both cases; I received a handoff and missed it. What I am certain of is that in both cases if I did receive a handoff and missed it on the first attempt; neither controller attempted to contact me a second time when I did not respond to their initial handoff. The first time this happened to me I did not file a report about it here. When I re-established contact with ft wayne; I was given a number to call; called it; spoke with a controller who seemed confused as to why I was calling him. I was later contacted by the FAA; spoke with an investigator and received a 'warning'. I am filing a report this time because; since receiving the first 'warning' I am very diligent about doing radio checks when the frequency I am on gets quiet and I note the time of every interaction with controllers. So it is distressing to me to have had it happen a second time in the same area of the country. I wonder if other pilots have experienced similar problems in the area? It seems to be a complex area for controllers; with multiple handoffs over relatively short legs. It would be understandable to me if other pilots were missing handoffs. I hope this report is helpful. Obviously I intend to double down on my attentiveness after a second occurrence. And if there are issues in the area I hope this report helps to lead to a solution.
Original NASA ASRS Text
Title: SR22 pilot experiences lost communications in the vicinity of UNV at 8000 feet; an area where he had experienced lost communications previously. Communication is regained on a different frequency and the radio appears to operate normally.
Narrative: I was on an IFR flight plan and was given a full route clearance; but after the first few legs I was cleared direct from TALLI intersection to my destination. I was speaking to New York [CENTER] at the time of the incident. I did a radio check at about XA:50 to XA:55 AM. Got a 'loud and clear' response from New York. At XB:08 I noticed that the controllers voice had changed and the transmissions had become somewhat fuzzy. I attempted to speak to the controller and received no response. At XB:10; after several attempts to raise the controller I contacted the tower at University Park Field on 128.7 and asked for the frequency of the next appropriate controller. I was given Cleveland 124.4. I immediately checked in with Cleveland; continued my flight and landed without incident. This is the second time this has happened to me on this route. The first time it happened a little further down the road when I was talking to Mansfield. I feel pretty sure that in both cases that I did not receive a handoff. But I cannot be certain of that. It is possible that in one or both cases; I received a handoff and missed it. What I AM certain of is that in both cases if I DID receive a handoff and missed it on the first attempt; neither controller attempted to contact me a second time when I did not respond to their initial handoff. The first time this happened to me I did not file a report about it here. When I re-established contact with Ft Wayne; I was given a number to call; called it; spoke with a controller who seemed confused as to why I was calling him. I was later contacted by the FAA; spoke with an investigator and received a 'warning'. I am filing a report this time because; since receiving the first 'warning' I am very diligent about doing radio checks when the frequency I am on gets quiet and I note the time of every interaction with controllers. So it is distressing to me to have had it happen a second time in the same area of the country. I wonder if other pilots have experienced similar problems in the area? It seems to be a complex area for controllers; with multiple handoffs over relatively short legs. It would be understandable to me if other pilots were missing handoffs. I hope this report is helpful. Obviously I intend to double down on my attentiveness after a second occurrence. And if there are issues in the area I hope this report helps to lead to a solution.
Data retrieved from NASA's ASRS site 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.