37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1243495 |
Time | |
Date | 201502 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors SID VNY1 |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
On departure out of bur we were initially flying the vny 1 departure from runway 15 via FMS navigation. We began the climbing right turn heading 210 when I checked in with socal departure and I thought I advised the controller that we were flying the vny 1 climbing to 4;000 ft. Then ATC advised fly heading 310 so I thought. My first officer went to heading mode and dialed in what we thought was our new heading of 310. So while we continued our right turn ATC asked why we are heading north when we should be on a heading vector of 210. I was confused by his query because I thought I was doing as instructed. I had mistaken his initial instruction to fly heading 210 instead my first officer flew heading 310. My first officer and [I] thought we were doing what was instructed. Then we were given another heading which I honestly don't remember which I believe was further north. Then finally a heading of 360 was given and we complied and then notified of a possible pilot deviation.discuss more thoroughly the departure with the PF and possible scenarios that could be expected. Then if anything is outside of what is expected then query ATC for clarification and confirm with the PF that the instruction that was heard was the same. Then if still understood incorrectly query ATC again.
Original NASA ASRS Text
Title: An air carrier crew departed BUR on the VNY 1 but were given a vector by SCT which they misunderstood; were given a second misunderstood vector; and finally got the correct heading.
Narrative: On departure out of BUR we were initially flying the VNY 1 departure from RWY 15 via FMS NAV. We began the climbing right turn HDG 210 when I checked in with SoCal departure and I thought I advised the controller that we were flying the VNY 1 climbing to 4;000 ft. Then ATC advised fly heading 310 so I thought. My FO went to heading mode and dialed in what we thought was our new heading of 310. So while we continued our right turn ATC asked why we are heading north when we should be on a heading vector of 210. I was confused by his query because I thought I was doing as instructed. I had mistaken his initial instruction to fly heading 210 instead my FO flew HDG 310. My FO and [I] thought we were doing what was instructed. Then we were given another HDG which I honestly don't remember which I believe was further north. Then finally a HDG of 360 was given and we complied and then notified of a possible pilot deviation.Discuss more thoroughly the departure with the PF and possible scenarios that could be expected. Then if anything is outside of what is expected then query ATC for clarification and confirm with the PF that the instruction that was heard was the same. Then if still understood incorrectly query ATC again.
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.