37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1348267 |
Time | |
Date | 201604 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | JFK.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Someone is going to get violated; or worse. I have flown [from] jfk several times over the past few weeks; and there have been several reports filed regarding problems with the clearance. I also know that the crew flying the trip opposite us has had similar problems and filed similar reports. Stop filing any routing out of jfk other than rbv J230 saame J6 zzzzz. I don't care if we can save a dollar by a more 'efficient' routing; new york is not going to allow us to fly it. We attempted to log on to controller pilot datalink communication (cpdlc) about 35-40 minutes prior to scheduled departure. The first time I have seen this; but the system would not allow us to log in - refused login. We tried several attempts with same results and I then decided to wait a few minutes to see if we were too early even though we have previously been advised via memo that waiting until inside of 30 minutes prior to block can result in problems. 5-10 minutes later we had the same results. We called clearance delivery and they said there was no flight plan on file. I sent a message to dispatch and they refiled us; along with a note back that they had no idea why the original flight plan dropped out of the system. While we were monitoring clearance delivery; he advised he had our clearance and would send it via cpdlc. We attempted to log in to cpdlc and were successful and our clearance came back promptly as: cleared to ZZZ airport SKORR3.rngrr then as filed. As we have been having issues with our clearance out of jfk for several weeks; I asked the first officer (first officer) to confirm our routing with clearance delivery. Clearance delivery verbally gave us a full route clearance that was the same as our flight departure paperwork/flight plan. Then we received another message via cpdlc that looked more like gibberish than a message. We discussed what this message meant; and I can't recall if we spoke with clear del again or not. After departure at 17;000 feet and heading on a vector to rbv; my first officer just had a feeling and asked ny departure what they showed for our route after rbv? It was not the same as we had been given while on the ground!!!! They showed J230 saame J6 zzzzz. This has got to stop. Someone is going to get violated; or we are going to have a separation conflict in new york airspace. I stated in my last report on this issue that I do not have confidence in the cpdlc/clearance system. This flight only reinforces my concerns. Someone has to figure out what is going on here and fix the problem.
Original NASA ASRS Text
Title: Captain reported consistently receiving a clearance route different from the one normally filed by company Dispatch. Captain recommended that the normal route filed by Dispatch be changed to that assigned by ATC.
Narrative: Someone is going to get violated; or worse. I have flown [from] JFK several times over the past few weeks; and there have been several reports filed regarding problems with the clearance. I also know that the crew flying the trip opposite us has had similar problems and filed similar reports. Stop filing any routing out of JFK other than RBV J230 SAAME J6 ZZZZZ. I don't care if we can save a dollar by a more 'efficient' routing; New York is not going to allow us to fly it. We attempted to log on to Controller Pilot Datalink Communication (CPDLC) about 35-40 minutes prior to scheduled departure. The first time I have seen this; but the system would not allow us to log in - REFUSED LOGIN. We tried several attempts with same results and I then decided to wait a few minutes to see if we were too early even though we have previously been advised via memo that waiting until inside of 30 minutes prior to block can result in problems. 5-10 minutes later we had the same results. We called Clearance Delivery and they said there was no flight plan on file. I sent a message to Dispatch and they refiled us; along with a note back that they had no idea why the original flight plan dropped out of the system. While we were monitoring Clearance Delivery; he advised he had our clearance and would send it via CPDLC. We attempted to log in to CPDLC and were successful and our clearance came back promptly as: CLEARED TO ZZZ ARPT SKORR3.RNGRR THEN AS FILED. As we have been having issues with our clearance out of JFK for several weeks; I asked the First Officer (FO) to confirm our routing with Clearance Delivery. Clearance Delivery verbally gave us a full route clearance that was the same as our Flight Departure paperwork/Flight Plan. Then we received another message via CPDLC that looked more like gibberish than a message. We discussed what this message meant; and I can't recall if we spoke with CLR DEL again or not. After departure at 17;000 feet and heading on a vector to RBV; my FO just had a feeling and asked NY Departure what they showed for our route after RBV? IT WAS NOT THE SAME AS WE HAD BEEN GIVEN WHILE ON THE GROUND!!!! They showed J230 SAAME J6 ZZZZZ. This has got to stop. Someone is going to get violated; or we are going to have a separation conflict in New York airspace. I stated in my last report on this issue that I do not have confidence in the CPDLC/clearance system. This flight only reinforces my concerns. Someone has to figure out what is going on here and fix the problem.
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.