 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Phl TRACON controller reported mistakenly handling an IFR aircraft as if it were VFR; leading to an MVA violation.
| Attributes | |
| ACN | 1721120 |
| Time | |
| Date | 202001 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | PHL.Airport |
| State Reference | PA |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X departed phl on an IFR flight plan for a nearby satellite airport. The aircraft was given runway heading and 3;000 feet by the tower. When the pilot checked in; he asked to maintain VFR on course. At that point I falsely assumed the aircraft was a VFR departure and began handling him as such. I cleared the aircraft out of the bravo at or below 2;500 feet; and verified they were familiar with an antenna north of the airport. The pilot leveled at 2;000 feet and flew through the 2;500 feet MVA associated with the antenna. When the aircraft got close to the destination airport; they asked to cancel IFR. The issue didn't even immediately register until I heard it later on the playback.I should check every departure strip more closely. The aircraft's data tag was properly displaying as IFR - I believe that seeing the weight category displayed; and not looking at it closely; made me assume the aircraft was VFR (just because there was some character in the lower right of the tag).
Original NASA ASRS Text
Title: PHL TRACON Controller reported mistakenly handling an IFR aircraft as if it were VFR; leading to an MVA violation.
Narrative: Aircraft X departed PHL on an IFR flight plan for a nearby satellite airport. The aircraft was given runway heading and 3;000 feet by the Tower. When the pilot checked in; he asked to maintain VFR on course. At that point I falsely assumed the aircraft was a VFR departure and began handling him as such. I cleared the aircraft out of the Bravo at or below 2;500 feet; and verified they were familiar with an antenna north of the airport. The pilot leveled at 2;000 feet and flew through the 2;500 feet MVA associated with the antenna. When the aircraft got close to the destination airport; they asked to cancel IFR. The issue didn't even immediately register until I heard it later on the playback.I should check every departure strip more closely. The aircraft's data tag was properly displaying as IFR - I believe that seeing the weight category displayed; and not looking at it closely; made me assume the aircraft was VFR (just because there was some character in the lower right of the tag).
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.