37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 887734 |
Time | |
Date | 201005 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Aircraft 1 | |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown Deviation - Track / Heading All Types |
Narrative:
I was working the r-side with training in progress on the D. I was fairly busy. I learned about aircraft X being cleared off the ground from srr to ZZZZ climbing to 14;000 for the terrain. The route apparently originally cleared 'as filed' for was: srr..elp..cen.UJ2.lto.UJ9.lap.UJ9.sjd..ZZZZ. The aircraft departed; I eventually radar identify him; then during his subsequent climb; I notice the aircraft was tracking much farther to the southwest than direct to elp; so I asked the pilot if was going direct elp. The pilot says no and indicated he was going to ruter intersection. At some point; the d-side started investigating for flight plans and discovered a second flight plan for this aircraft in the system; also going to ZZZZ; but that apparently wasn't visible on the uret at the time they cleared the aircraft. The route the aircraft thought he was 'cleared as filed' for; and what he was performing was: srr..ruter.J13.becon.UT13.chx.UJ8.LMM.UJ51.sjd..ZZZZ. This is a fair departure from the route we thought we cleared them for. Upon inquiring the pilot further; I was able to obtain some information on how their company files flight plans. He stated to me that they go through a company and that they were responsible for the flight plans; and the pilots just go off what was faxed to them; or words to that effect. The pilot seemed awfully nonchalant about the whole thing; but that's another issue. In any case; I'm not entirely sure whether this is a flight plan issued through the FSS; with this company; or whether my d-side actually looked to see if there were multiple flight plans in the machine. The trainer stated that there was only one srr flight plan showing at the time; so they didn't feel it necessary to investigate for multiple flight plans; which is fair. A logic check in the system to disallow multiple flight plans for the same aircraft going to the same destination. An ability for FSS to remove proposed flight plans perhaps if a pilot updates their filed route or p-time (if that doesn't already exist.)
Original NASA ASRS Text
Title: ZAB Controller described a confused IFR departure flight from SRR to MMSD with some concern for terrain clearance; noting multiple flight plans and routes on file.
Narrative: I was working the R-Side with training in progress on the D. I was fairly busy. I learned about Aircraft X being cleared off the ground from SRR to ZZZZ climbing to 14;000 for the terrain. The route apparently originally cleared 'as filed' for was: SRR..ELP..CEN.UJ2.LTO.UJ9.LAP.UJ9.SJD..ZZZZ. The aircraft departed; I eventually RADAR identify him; then during his subsequent climb; I notice the aircraft was tracking much farther to the SW than direct to ELP; so I asked the pilot if was going direct ELP. The pilot says no and indicated he was going to RUTER intersection. At some point; the D-Side started investigating for flight plans and discovered a second flight plan for this aircraft in the system; also going to ZZZZ; but that apparently wasn't visible on the URET at the time they cleared the aircraft. The route the aircraft thought he was 'cleared as filed' for; and what he was performing was: SRR..RUTER.J13.BECON.UT13.CHX.UJ8.LMM.UJ51.SJD..ZZZZ. This is a fair departure from the route we thought we cleared them for. Upon inquiring the pilot further; I was able to obtain some information on how their company files flight plans. He stated to me that they go through a company and that they were responsible for the flight plans; and the pilots just go off what was faxed to them; or words to that effect. The pilot seemed awfully nonchalant about the whole thing; but that's another issue. In any case; I'm not entirely sure whether this is a flight plan issued through the FSS; with this company; or whether my D-Side actually looked to see if there were multiple flight plans in the machine. The trainer stated that there was only one SRR flight plan showing at the time; so they didn't feel it necessary to investigate for multiple flight plans; which is fair. A logic check in the system to disallow multiple flight plans for the same aircraft going to the same destination. An ability for FSS to remove proposed flight plans perhaps if a pilot updates their filed route or P-Time (if that doesn't already exist.)
Data retrieved from NASA's ASRS site as of April 2012 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.