Narrative:

This is not an as soon as possible but a report to evaluate the safety of operation when given the PEBLE6 departure out of san. This was not a pilot deviation but we were asked to call the supervisor when we landed. The peble 6 is not in the FMS database nor is it an RNAV SID so per the departure; I programed and briefed that after departure; we were to fly a 293 heading till crossing the 170 radial off ocn. At that point; the pilot flying also cross referenced his VOR to do the same.after the 170 degree radial (observed and verified by both pilots); was crossed; I called for a heading of 318 to intercept the mzb 293 radial to meldy. We had verified that there were no NOTAMS for the ocn VOR. As mentioned; it was flown exactly as published and exactly as he had done two weeks earlier and multiple times. When I spoke to [name redacted] in san diego; she was adamant in informing us it was not a pilot deviation but she said it looked like our plane turned closer to the 150 radial instead of the 170. She also said that the plane that took off behind us on the same departure turned early as well and they need to evaluate the procedure.she also told me that they had had an issue with jet a few months back (their FMS did not contain the PEBLE6 departure either) but thought they had resolved it. I told her both VOR's were indicating the 170. I asked; if in the future; should we refuse the departure and what could they give us in lieu of. She said a heading and altitude with radar vectors but she wanted to have the procedure analyzed to figure out what is going wrong. She then proceeded to invite us out to see the facility next time we were in san diego.

Google
 

Original NASA ASRS Text

Title: CL-300 flight crew reported issues with SAN departure procedure.

Narrative: This is not an ASAP but a report to evaluate the safety of operation when given the PEBLE6 departure out of SAN. This was not a pilot deviation but we were asked to call the supervisor when we landed. The PEBLE 6 is not in the FMS database nor is it an RNAV SID so per the departure; I programed and briefed that after departure; we were to fly a 293 heading till crossing the 170 radial off OCN. At that point; the pilot flying also cross referenced his VOR to do the same.After the 170 degree radial (observed and verified by both pilots); was crossed; I called for a heading of 318 to intercept the MZB 293 radial to MELDY. We had verified that there were no NOTAMS for the OCN VOR. As mentioned; it was flown exactly as published and exactly as he had done two weeks earlier and multiple times. When I spoke to [name redacted] in San Diego; she was adamant in informing us it was not a pilot deviation but she said it looked like our plane turned closer to the 150 radial instead of the 170. She also said that the plane that took off behind us on the same departure turned early as well and they need to evaluate the procedure.She also told me that they had had an issue with Jet a few months back (their FMS did not contain the PEBLE6 departure either) but thought they had resolved it. I told her both VOR's were indicating the 170. I asked; if in the future; should we refuse the departure and what could they give us in lieu of. She said a heading and altitude with radar vectors but she wanted to have the procedure analyzed to figure out what is going wrong. She then proceeded to invite us out to see the facility next time we were in San Diego.

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.