 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
PA31 pilot reports departing rmn VFR to pick up an IFR flight plan airborne. An IFR clearance is issued then a few minutes later it is canceled and the reporter is told to turn 20 degrees right; descend to a VFR altitude and contact pct on a different frequency. The new controller points out traffic and the reporter deduces the IFR clearance cancellation was due to this traffic.
| Attributes | |
| ACN | 1221763 |
| Time | |
| Date | 201411 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PCT.TRACON |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | PA-31 Navajo/Chieftan/Mojave/T1040 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying |
| Qualification | Flight Crew Commercial Flight Crew Glider Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 25 Flight Crew Total 4600 Flight Crew Type 1800 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC |
| Miss Distance | Horizontal 0 Vertical 300 |
Narrative:
I departed rmn and obtained an IFR clearance with instructions to report over brooke VOR squawking xyzx. We departed VFR as requested. Reported to potomac approach over brooke. Instructed to proceed direct to ott VOR at 4000 MSL consider ourselves IFR. A few minutes later controller instructed us to turn right 20 degrees and our IFR was terminated; next controller instructed us to descend to a VFR altitude and switch frequencies to a new controller and tell him we were VFR. King air traffic was called out to us before the switch which controller stated was not under her control. Reported into the new frequency and controller had no idea who we were or that we were previously IFR and IFR terminated by controller. King air traffic called out to us by new controller and king air and we reported each other in sight. King air military traffic crossed over us less than 500 feet vertical separation. Controller resumed our flight as IFR after inquiring our destination. I believe the initial controller canceled our IFR clearance when she realized there was going to be a conflict rather than issuing vectors for separation or coordinating with the adjacent sector controller. This action caused confusion by the next controller and ourselves in the cockpit. This action for the controller to initiate termination of IFR after accepting a flight as IFR is potentially dangerous to the safe conduct of a flight.
Original NASA ASRS Text
Title: PA31 pilot reports departing RMN VFR to pick up an IFR flight plan airborne. An IFR clearance is issued then a few minutes later it is canceled and the reporter is told to turn 20 degrees right; descend to a VFR altitude and contact PCT on a different frequency. The new Controller points out traffic and the reporter deduces the IFR clearance cancellation was due to this traffic.
Narrative: I departed RMN and obtained an IFR clearance with instructions to report over Brooke VOR squawking XYZX. We departed VFR as requested. Reported to Potomac approach over Brooke. Instructed to proceed direct to OTT VOR at 4000 MSL consider ourselves IFR. A few minutes later controller instructed us to turn right 20 degrees and our IFR was terminated; next controller instructed us to descend to a VFR altitude and switch frequencies to a new controller and tell him we were VFR. King Air traffic was called out to us before the switch which controller stated was not under her control. Reported into the new frequency and Controller had no idea who we were or that we were previously IFR and IFR terminated by controller. King Air traffic called out to us by new controller and King Air and we reported each other in sight. King Air military traffic crossed over us less than 500 feet vertical separation. Controller resumed our flight as IFR after inquiring our destination. I believe the initial controller canceled our IFR clearance when she realized there was going to be a conflict rather than issuing vectors for separation or coordinating with the adjacent sector controller. This action caused confusion by the next controller and ourselves in the cockpit. This action for the controller to initiate termination of IFR after accepting a flight as IFR is potentially dangerous to the safe conduct of a flight.
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.