37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1183781 |
Time | |
Date | 201406 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BDL.Airport |
State Reference | CT |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 3 Flight Crew Total 540 Flight Crew Type 8 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Miss Distance | Horizontal 6000 Vertical 200 |
Narrative:
Immediately prior to flight I briefed with a CFI and specifically discussed that aircraft was not IFR ready and that I would need to maintain VFR at all times. I filed aircraft type as P28R/U but direct 9b1. I filed and was not able to select VFR-on-top or enter a comment (e.g.; 'training flight'). I did select a VFR altitude; but was assigned 11;000. I did not request VFR-on-top after I was in the air. I was not expecting GPS fixes and expected to fly a visual approach into 9b1. ATC asked me to confirm that I was slant uniform. I confirmed that I was. The next question was how I was navigating direct. I admitted that I had an ipad for GPS but that it was not an IFR system. I was instructed to proceed direct dreem. I tried dream in my ipad; but did not find the waypoint. I advised ATC that I was unable to find it and asked for a vector. I was given a vector which appeared to be my current heading. Had ATC spelled dreem for me; I probably would have found it. I was flying in VMC at all times and descended from 11;000 ft to 9;000 ft; then to 7;000 ft maintaining VFR. Shortly after I leveled out at 7;000 ft; ATC instructed me to descend to 5;000 ft and proceed direct dreem. I was looking for dream on the IFR low altitude chart on my ipad. ATC advised that there was traffic at 12:00; to turn left to 360; and warned that I had descended below assigned altitude. I was able to see the other aircraft and immediately turned left and began climbing back to 5;000 ft. I reported to ATC that I had the traffic in sight. After returning to 5;000 ft; I believe I was back to boston center who advised that there was a possible pilot deviation and that the next controller would probably be asking me to call number. When handed back to bradley approach; I advised that I had located dreem (on low IFR chart) and was told to proceed direct to dreem. I know that it is not unusual for a controller to 'chew out' a pilot for a mistake. But not all controllers do this. This was my first time being chewed out. My observation is that it was a bad idea. Even though I tried to remain calm; I found that it had caused me to be stressed and made it harder to focus on my landing. I think the chewing out should have waited until I was safely on the ground. I believe that chewing out a pilot in the air compromises safety. I should have cancelled IFR earlier. ATC should have given me vectors rather than a GPS fix based on my type '/U'. ATC might have inquired whether I wished to proceed VFR. This was a case where I did not know the best way for ATC to continue navigation. My original clearance was direct 9b1. The primary cause of my failure to stop descent was my attention diverted to finding a GPS waypoint when I had not briefed GPS waypoints and did not have the spelling. Also contributing to the event was my filing direct to my destination which left ATC expecting that I had GPS. ATC should have been able to recover by treating me as having a GPS failure or GPS outage. Repeated instructions from ATC for me to proceed direct dreem created a sense of necessity to find dream on the map which distracted me from the important duty of leveling out at 5;000 ft. The difference between dreem and 9b1 would have been a very slight heading change. I probably could have proceeded on course or flown 1 or 2 degrees left of course. Finding dreem was probably quite unnecessary. In retrospect; I wish I had cancelled IFR when ATC asked me how I was navigating.
Original NASA ASRS Text
Title: PA28 pilot reports filing an IFR flight plan /U direct to his destination in a non IFR aircraft using an iPad for navigation. This leads to confusion on the part of ATC and an altitude deviation on the part of the reporter.
Narrative: Immediately prior to flight I briefed with a CFI and specifically discussed that aircraft was not IFR ready and that I would need to maintain VFR at all times. I filed aircraft type as P28R/U but DIRECT 9B1. I filed and was not able to select VFR-on-top or enter a comment (e.g.; 'training flight'). I did select a VFR altitude; but was assigned 11;000. I did not request VFR-on-top after I was in the air. I was not expecting GPS fixes and expected to fly a visual approach into 9B1. ATC asked me to confirm that I was slant uniform. I confirmed that I was. The next question was how I was navigating DIRECT. I admitted that I had an iPad for GPS but that it was not an IFR system. I was instructed to proceed direct DREEM. I tried DREAM in my iPad; but did not find the waypoint. I advised ATC that I was unable to find it and asked for a vector. I was given a vector which appeared to be my current heading. Had ATC spelled DREEM for me; I probably would have found it. I was flying in VMC at all times and descended from 11;000 FT to 9;000 FT; then to 7;000 FT maintaining VFR. Shortly after I leveled out at 7;000 FT; ATC instructed me to descend to 5;000 FT and proceed DIRECT DREEM. I was looking for DREAM on the IFR low altitude chart on my iPad. ATC advised that there was traffic at 12:00; to turn left to 360; and warned that I had descended below assigned altitude. I was able to see the other aircraft and immediately turned left and began climbing back to 5;000 FT. I reported to ATC that I had the traffic in sight. After returning to 5;000 FT; I believe I was back to Boston Center who advised that there was a possible pilot deviation and that the next controller would probably be asking me to call number. When handed back to Bradley Approach; I advised that I had located DREEM (on low IFR chart) and was told to proceed direct to DREEM. I know that it is not unusual for a Controller to 'chew out' a pilot for a mistake. But not all controllers do this. This was my first time being chewed out. My observation is that it was a bad idea. Even though I tried to remain calm; I found that it had caused me to be stressed and made it harder to focus on my landing. I think the chewing out should have waited until I was safely on the ground. I believe that chewing out a pilot in the air compromises safety. I should have cancelled IFR earlier. ATC should have given me vectors rather than a GPS fix based on my type '/U'. ATC might have inquired whether I wished to proceed VFR. This was a case where I did not know the best way for ATC to continue navigation. My original clearance was DIRECT 9B1. The primary cause of my failure to stop descent was my attention diverted to finding a GPS waypoint when I had not briefed GPS waypoints and did not have the spelling. Also contributing to the event was my filing direct to my destination which left ATC expecting that I had GPS. ATC should have been able to recover by treating me as having a GPS failure or GPS outage. Repeated instructions from ATC for me to proceed DIRECT DREEM created a sense of necessity to find DREAM on the map which distracted me from the important duty of leveling out at 5;000 FT. The difference between DREEM and 9B1 would have been a very slight heading change. I probably could have proceeded on course or flown 1 or 2 degrees left of course. Finding DREEM was probably quite unnecessary. In retrospect; I wish I had cancelled IFR when ATC asked me how I was navigating.
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.