 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot departed sbp on a crepe three departure but did not use the i-sbp runway 29 localizer course outbound and so was off track on the departure.
| Attributes | |
| ACN | 889398 |
| Time | |
| Date | 201005 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SBP.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID CREPE THREE |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | ILS/VOR |
| Person 1 | |
| Function | Single Pilot |
| Qualification | Flight Crew Private Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 20 Flight Crew Total 1020 Flight Crew Type 897 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Off course on crepe three departure because HSI was set to outbound course of 290 instead of the back course for the localizer. I thought it was an extension of an ILS for runway 29. However; it was a back course for the ILS on runway 11. There is no localizer approach for runway 29; but as I was unfamiliar with the airport I did not know that. Root cause was the NOAA departure plates lack of clear specification that it is a back course. The only hint is the fact that the shading is on the bottom of the localizer symbol. Also there is a note about watching for opposing traffic on the localizer course which now makes more sense. This can be prevented in the future if the departure plate clearly states that the localizer is back on course.
Original NASA ASRS Text
Title: A Pilot departed SBP on a CREPE THREE DEPARTURE but did not use the I-SBP Runway 29 localizer course outbound and so was off track on the departure.
Narrative: Off course on CREPE THREE Departure because HSI was set to outbound course of 290 instead of the back course for the localizer. I thought it was an extension of an ILS for Runway 29. However; it was a back course for the ILS on Runway 11. There is no localizer approach for Runway 29; but as I was unfamiliar with the airport I did not know that. Root cause was the NOAA departure plates lack of clear specification that it is a back course. The only hint is the fact that the shading is on the bottom of the localizer symbol. Also there is a note about watching for opposing traffic on the localizer course which now makes more sense. This can be prevented in the future if the departure plate clearly states that the localizer is back on course.
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.