37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 994844 |
Time | |
Date | 201202 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CMA.Airport |
State Reference | CA |
Environment | |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Other Obstacle Departure Procedure |
Flight Plan | IFR |
Component | |
Aircraft Component | Aero Charts |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 14000 Flight Crew Type 4500 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Departing from runway 26 in camarillo; we were cleared to depart using the published obstacle departure procedure (odp). I misread the procedure which ends with left turn direct the cma VOR. This is what we briefed and flew. The procedure requires a right turn to intercept the 265 radial and then left direct the cma VOR. I have not flown this procedure before and was not familiar. However; in my opinion the core cause of my oversight was twofold. 1) R265 at left edge of chart; I misread as runway 26. Therefore believed it was the start of odp for runway 26 cma. 2) this turn made sense knowing I was turning away from terrain and housing for noise abatement and toward the normal pattern for the airport. Climbing through 2;000 ft the controller at magu asked if we were receiving the camarillo VOR; which I thought was unusual. This is the only reason I took a second look at the odp and realized my mistake. I could have easily not caught this mistake. The controller was not upset; nor did he seem to recognize our error. There was no other traffic or conflict due to early departure before tower was open in camarillo. I have a suggestion regarding charting. If each runway that has an odp was published in its own box; a mistake like this would be harder to make. This won't happen to me again.
Original NASA ASRS Text
Title: A pilot reported turning left after a CMA Runway 26 departure; because he misread the CMA commercial chart Obstacle Departure Procedure (ODP) which formats the Runway 8 and Runway 26 procedures without sufficient textual separation.
Narrative: Departing from Runway 26 in Camarillo; we were cleared to depart using the published Obstacle Departure Procedure (ODP). I misread the procedure which ends with left turn direct the CMA VOR. This is what we briefed and flew. The procedure requires a right turn to intercept the 265 radial and then left direct the CMA VOR. I have not flown this procedure before and was not familiar. However; in my opinion the core cause of my oversight was twofold. 1) R265 at left edge of chart; I misread as Runway 26. Therefore believed it was the start of ODP for Runway 26 CMA. 2) This turn made sense knowing I was turning away from terrain and housing for noise abatement and toward the normal pattern for the airport. Climbing through 2;000 FT the Controller at Magu asked if we were receiving the Camarillo VOR; which I thought was unusual. This is the only reason I took a second look at the ODP and realized my mistake. I could have easily not caught this mistake. The Controller was not upset; nor did he seem to recognize our error. There was no other traffic or conflict due to early departure before Tower was open in Camarillo. I have a suggestion regarding charting. If each runway that has an ODP was published in its own box; a mistake like this would be harder to make. This won't happen to me again.
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.