37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1124890 |
Time | |
Date | 201310 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | N90.TRACON |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID KENNEDY 1 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Out of jfk we received the kennedy one departure breezy point climb. Captain was acting as pilot flying and me as pilot monitoring. All briefings were performed as standard. We even stopped twice to discuss the departure and we agreed to use the autopilot for the RNAV departure. After takeoff from runway 31L we were handed off to departure. During the climb and after performing the after takeoff checklist; it came to my attention that there was a discontinuity after cri. Immediately I focused on the departure chart and saw neither the rngrr intersection nor the 223 radial were depicted on the FMS. Simultaneously the controller was aware that we were not making the turn and called us saying to initiate the turn and I quote; 'there is something with you guys that don't make the turn. Someday things are going to get really ugly up there.' the captain with the heading bug starts to figure out the problem at this time; which was a discontinuity on the FMS. I called back the controller telling him that we are trying to make the turn and confessed that at the moment we don't have the fix on the FMS. Five seconds later the controller commanded a heading of 180 that we acknowledge complying with it. Finally after clearing us back to the route he gave us a telephone number to contact and again expressed that is a problem with our company airplanes and maybe we should involve the chief pilots because is something that is been happening a lot. Through the flight we tried to figure out what was the mistake and why we get ourselves in that situation. Once we land we agreed to file a report and the captain called the telephone number provided. The answer from the ny [TRACON] was that the controller left his station for the day but there wasn't any lateral or vertical deviation.I believe that we do everything in our reach to not get in an undesired situation. We follow the briefing as standard and try to use the automation as much as we could; maybe we relied too much on the FMS and that could be our error. I would like to have an explanation of what happened or what we did wrong during the operation and if it is really a constant problem when we takeoff from runway 31L. [I would like to] use this as a learning experience because I definitely don't want to find myself in this situation again ever.
Original NASA ASRS Text
Title: An air carrier with a Collins FMS departed JFK on the Kennedy One Breezy Point climb Departure and sometime after takeoff the turn to Canarsie dropped out leaving a route discontinuity which ATC stated was happening frequently with his Company's aircraft.
Narrative: Out of JFK we received the KENNEDY ONE DEPARTURE BREEZY POINT climb. Captain was acting as Pilot Flying and me as Pilot Monitoring. All briefings were performed as standard. We even stopped twice to discuss the departure and we agreed to use the autopilot for the RNAV departure. After takeoff from Runway 31L we were handed off to Departure. During the climb and after performing the After Takeoff checklist; it came to my attention that there was a discontinuity after CRI. Immediately I focused on the departure chart and saw neither the RNGRR Intersection nor the 223 radial were depicted on the FMS. Simultaneously the Controller was aware that we were not making the turn and called us saying to initiate the turn and I quote; 'There is something with you guys that don't make the turn. Someday things are going to get really ugly up there.' The Captain with the heading bug starts to figure out the problem at this time; which was a discontinuity on the FMS. I called back the Controller telling him that we are trying to make the turn and confessed that at the moment we don't have the fix on the FMS. Five seconds later the Controller commanded a heading of 180 that we acknowledge complying with it. Finally after clearing us back to the route he gave us a telephone number to contact and again expressed that is a problem with our company airplanes and maybe we should involve the chief pilots because is something that is been happening a lot. Through the flight we tried to figure out what was the mistake and why we get ourselves in that situation. Once we land we agreed to file a report and the Captain called the telephone number provided. The answer from the NY [TRACON] was that the Controller left his station for the day but there wasn't any lateral or vertical deviation.I believe that we do everything in our reach to not get in an undesired situation. We follow the briefing as standard and try to use the automation as much as we could; maybe we relied too much on the FMS and that could be our error. I would like to have an explanation of what happened or what we did wrong during the operation and if it is really a constant problem when we takeoff from Runway 31L. [I would like to] use this as a learning experience because I definitely don't want to find myself in this situation again ever.
Data retrieved from NASA's ASRS site as of July 2013 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.