Heading track altitude deviation altitude overshot in climb.

Attributes
ACN	299969
Time
Date	199503
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lgb
State Reference	CA
Altitude	msl bound lower : 1600 msl bound upper : 4000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : lax tower : lgb
Operator	general aviation : corporate
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Navigation In Use	Other Other
Flight Phase	climbout : initial cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : first officer oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 150 flight time total : 8000 flight time type : 2500
ASRS Report	299969
Person 2
Affiliation	Other
Function	flight crew : single pilot flight crew : captain
Qualification	pilot : commercial pilot : atp pilot : instrument
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

All company pilots are type rated and we swap seats each leg. I was PIC in right seat. First time with this first officer. Departure clearance was runway heading 300 degrees to 1400 ft or 1600 ft, turn left to 180 degrees. When told to taxi into position and hold, I crosschecked first officer's heading bug to see if it was set to runway heading, or 180 degree. It was neither. It was set at 270 degree. As I started to say something to him we were cleared for takeoff. I continued with runway checklist items. Very shortly after takeoff we had a heading comparator light, at which time I noticed we were going through about 1800 ft. I told him to turn to 270 degrees (the last heading I saw on his bug!!) he did this. He later stated that he knew it was a 180 degree heading as we discussed in the pre takeoff briefing, but didn't say anything. We switched to departure and tried to figure out what heading was good. By then I also realized we should have been on a 180 degree heading and started to turn to 180 degrees. About this time departure asked us our heading to which I replied turning to 180 degrees. A discussion started as to what tower assigned us, and I told them 180 degrees. They then gave us further left to 160 degrees. No same altitude traffic was issued so I don't know if we were close to anyone or not. No further comments from departure. During this flight I was flying with a very bad cold. No medication, just feeling rotten, not thinking as quickly and carefully as I should have. That was the first mistake. Second was not correcting the first officer's heading bug. When the distrs started, I just called out the last thing I saw. Also, the departure clearance was covered by the airport diagram so I didn't have a quick reference to it. After we got home I canceled my next trip because of sickness. Not 100 percent. I am not going to count on memory for clrncs, they will be where they will be easy to get to. Also, I plan on advising all first officer's I fly with to speak up if they think something isn't correct. Strangely, this first officer just returned from cockpit resource management training. You would have thought he could have spoken up. Still my fault though.

Original NASA ASRS Text

Title: HDG TRACK ALTDEV ALT OVERSHOT IN CLB.

Narrative: ALL COMPANY PLTS ARE TYPE RATED AND WE SWAP SEATS EACH LEG. I WAS PIC IN R SEAT. FIRST TIME WITH THIS FO. DEP CLRNC WAS RWY HDG 300 DEGS TO 1400 FT OR 1600 FT, TURN L TO 180 DEGS. WHEN TOLD TO TAXI INTO POS AND HOLD, I XCHKED FO'S HDG BUG TO SEE IF IT WAS SET TO RWY HDG, OR 180 DEG. IT WAS NEITHER. IT WAS SET AT 270 DEG. AS I STARTED TO SAY SOMETHING TO HIM WE WERE CLRED FOR TKOF. I CONTINUED WITH RWY CHKLIST ITEMS. VERY SHORTLY AFTER TKOF WE HAD A HDG COMPARATOR LIGHT, AT WHICH TIME I NOTICED WE WERE GOING THROUGH ABOUT 1800 FT. I TOLD HIM TO TURN TO 270 DEGS (THE LAST HDG I SAW ON HIS BUG!!) HE DID THIS. HE LATER STATED THAT HE KNEW IT WAS A 180 DEG HDG AS WE DISCUSSED IN THE PRE TKOF BRIEFING, BUT DIDN'T SAY ANYTHING. WE SWITCHED TO DEP AND TRIED TO FIGURE OUT WHAT HDG WAS GOOD. BY THEN I ALSO REALIZED WE SHOULD HAVE BEEN ON A 180 DEG HDG AND STARTED TO TURN TO 180 DEGS. ABOUT THIS TIME DEP ASKED US OUR HDG TO WHICH I REPLIED TURNING TO 180 DEGS. A DISCUSSION STARTED AS TO WHAT TWR ASSIGNED US, AND I TOLD THEM 180 DEGS. THEY THEN GAVE US FURTHER L TO 160 DEGS. NO SAME ALT TFC WAS ISSUED SO I DON'T KNOW IF WE WERE CLOSE TO ANYONE OR NOT. NO FURTHER COMMENTS FROM DEP. DURING THIS FLT I WAS FLYING WITH A VERY BAD COLD. NO MEDICATION, JUST FEELING ROTTEN, NOT THINKING AS QUICKLY AND CAREFULLY AS I SHOULD HAVE. THAT WAS THE FIRST MISTAKE. SECOND WAS NOT CORRECTING THE FO'S HDG BUG. WHEN THE DISTRS STARTED, I JUST CALLED OUT THE LAST THING I SAW. ALSO, THE DEP CLRNC WAS COVERED BY THE ARPT DIAGRAM SO I DIDN'T HAVE A QUICK REF TO IT. AFTER WE GOT HOME I CANCELED MY NEXT TRIP BECAUSE OF SICKNESS. NOT 100 PERCENT. I AM NOT GOING TO COUNT ON MEMORY FOR CLRNCS, THEY WILL BE WHERE THEY WILL BE EASY TO GET TO. ALSO, I PLAN ON ADVISING ALL FO'S I FLY WITH TO SPEAK UP IF THEY THINK SOMETHING ISN'T CORRECT. STRANGELY, THIS FO JUST RETURNED FROM COCKPIT RESOURCE MGMNT TRAINING. YOU WOULD HAVE THOUGHT HE COULD HAVE SPOKEN UP. STILL MY FAULT THOUGH.

Data retrieved from NASA's ASRS site as of July 2007 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.