37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 881920 |
Time | |
Date | 201003 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PBI.Airport |
State Reference | FL |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Person 1 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown |
Narrative:
Clearance over pre departure clearance showed revised segment as blufi ramjt then filed route. I'd never seen this before at pbi; so I called clearance delivery. They said they showed nothing like that sent over pre departure clearance and then read me a full route clearance. Blufi doesn't live on any arrival or departure at pbi. There is a blufi arrival to mia and a blufi intersection on V295. ATC at pbi said as far as they knew it was a reference to an ATC radar sector. Blufi actually lives just a little northwest of A699 to which our 'real' clearance said we would be vectored; the clearance we got; and would have flown had we combined the revised and filed routes as we are told to do; would have been wrong. In fact; no one at the pbi ATC facility even knew what it was and insisted; correctly I'm sure; that they didn't have any record of a clearance like we got over the pre departure clearance. There was not even a reference to the PB6 departure which was part of our actual clearance and should have contained the only altitude restriction in the ATC clearance....there was none. This happened again; except this time pbi ATC knew about it; sort of. When I inquired about it again with clearance delivery they thanked me for checking and then read me a full route. This time the PB6 departure was in pre departure clearance. In both cases the incorrect blufi ramjt came at the beginning of the pre departure clearance in a revised segment. It used to be no harm; no foul with ATC but now they will pursue a violation for a minor navigation deviation.
Original NASA ASRS Text
Title: Air carrier flight crew departing PBI described a very confusing clearance issue when PDC clearance contained unknown/uncertain fix points; the reporter also indicating ATC was unsure of fix points as well.
Narrative: Clearance over PDC showed revised segment as BLUFI RAMJT then filed route. I'd never seen this before at PBI; so I called Clearance Delivery. They said they showed nothing like that sent over PDC and then read me a full route clearance. BLUFI doesn't live on any arrival or departure at PBI. There is a BLUFI arrival to MIA and a BLUFI intersection on V295. ATC at PBI said as far as they knew it was a reference to an ATC Radar Sector. BLUFI actually lives just a little northwest of A699 to which our 'real' clearance said we would be vectored; the clearance we got; and would have flown had we combined the revised and filed routes as we are told to do; would have been wrong. In fact; no one at the PBI ATC facility even knew what it was and insisted; correctly I'm sure; that they didn't have any record of a clearance like we got over the PDC. There was not even a reference to the PB6 departure which was part of our actual clearance and should have contained the only altitude restriction in the ATC clearance....there was none. This happened again; except this time PBI ATC knew about it; sort of. When I inquired about it again with Clearance Delivery they thanked me for checking and then read me a full route. This time the PB6 departure was in PDC. In both cases the incorrect BLUFI RAMJT came at the beginning of the PDC in a revised segment. It used to be no harm; no foul with ATC but now they will pursue a violation for a minor NAV deviation.
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.