37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1340863 |
Time | |
Date | 201603 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation X (C750) |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Preflight preparation involved flight plan review and notams with applicable information. In the NOTAM section of our plight plan package there was a note (jeppesen [navdata] change notice): PEBLE6 RWY27 initial course should be 275 degrees. When departing from 27 and handed off to departure I checked in with altitude passing and on a 275 heading. He asked if we were on the PEBLE6 and I said affirmative. About a minute later he asked if we were on the PEBLE6 again and I said steady on 275 degree heading. About 30 sec later he gave us direct peble intersection and then a phone number for a possible navigation deviation. Our flight continued normally.after shutdown I called our dispatch manager and asked about where we get NOTAM info and he indicated from jeppesen. He also indicated that there have been some issues with notams not dropping out when they expire. I then called so cal center with the number given by ATC. I explained all of the above and he took the info he needed; gave another number and [I] explained again with the airspace manager. [He] said it would go to FSDO. We were given wrong information on a NOTAM that apparently did not exist. On departure control [perhaps] if he saw a deviation he could have given corrective heading. (We have visual with aircraft that departed ahead of us). The concern for me as I expressed to everyone I spoke with; future releases of [company] aircraft with this bad information.the error occurred internally through the vendor and dispatch and as flight crews we could not have known. I will now carry additional personal ipad with foreflight and double check against nos and direct FAA info. Note: at no time was this flight in danger; preceding aircraft was in visual contact and no TA generated.
Original NASA ASRS Text
Title: CE-750 flight crew reported they experienced a track deviation departing SAN when they followed heading guidance from a NOTAM that was not in effect at the time.
Narrative: Preflight preparation involved flight plan review and NOTAMs with applicable information. In the NOTAM section of our plight plan package there was a note (Jeppesen [NAVDATA] change notice): PEBLE6 RWY27 initial course should be 275 degrees. When departing from 27 and handed off to departure I checked in with altitude passing and on a 275 heading. He asked if we were on the PEBLE6 and I said affirmative. About a minute later he asked if we were on the PEBLE6 again and I said steady on 275 degree heading. About 30 sec later he gave us direct PEBLE intersection and then a phone number for a possible NAV Deviation. Our flight continued normally.After shutdown I called our Dispatch manager and asked about where we get NOTAM info and he indicated from JEPPESEN. He also indicated that there have been some issues with NOTAMs not dropping out when they expire. I then called So Cal Center with the number given by ATC. I explained all of the above and he took the info he needed; gave another number and [I] explained again with the airspace MGR. [He] said it would go to FSDO. We were given wrong information on a NOTAM that apparently did not exist. On departure control [perhaps] if he saw a deviation he could have given corrective heading. (We have visual with aircraft that departed ahead of us). The concern for me as I expressed to everyone I spoke with; future releases of [Company] aircraft with this bad information.The error occurred internally through the vendor and Dispatch and as flight crews we could not have known. I will now carry additional personal iPad with ForeFlight and double check against NOS and Direct FAA info. Note: At no time was this flight in danger; preceding aircraft was in visual contact and no TA generated.
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.