37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1624100 |
Time | |
Date | 201903 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | WHP.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | VFR Route |
Flight Plan | None |
Person 1 | |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 84 Flight Crew Total 4300 Flight Crew Type 60 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Departing VFR from kwhp. I had received a squawk code and informed tower of my request for flight following and my on course heading of 055. I'm not based at kwhp and not familiar with the local 'standard' procedures. On takeoff clearance from tower; the tower controller instructed me to make a left downwind departure. After takeoff; I initiated a left turn above 400 feet and within 1/2 mile of the airfield. I followed this with a turn to left downwind. Upon reaching midfield left downwind; I turned right out of traffic to a 030 heading. Shortly thereafter the controller came on the radio and yelled that I was entering burbank airspace and was a traffic conflict. He then yelled at me that I was supposed to do the left downwind departure. I informed the controller that I did in fact fly to left downwind midfield then turned out of traffic. He responded with a lecture on if I'm not local familiar; that I need to inform him and how I am a conflict to traffic going into burbank airspace; but no traffic call was given. I'm not a local based aircraft. I just flew in 45 minutes prior and at that time informed him that I'm not familiar. He continued to tell me that I was supposed to continue left downwind until he told me otherwise. These instructions were not given in the takeoff clearance. I responded saying that 'I will turn back toward the airfield to downwind' he responded 'no' but did not give any further direction or traffic calls. A long silence from the controller followed. I picked up a visual on a business jet on final into burbank; stopped my climb and maintained visual separation. Upon us passing; he said; do you have a visual on the [traffic]? I responded affirmative. Following this the controller then lectured me again of what he expected me to do. I informed the controller; 'my mistake; I flew to left downwind then departed the pattern from midfield; I was under the impression that was the departure instruction.' the controller then responded with; 'you are correct it is your mistake; see what your mistake almost caused.' following this a hand off to approach occurred.in the misunderstanding of the departure; based off the squawk code and the discussion of on course heading it was my assumption that I was now a class C participant. I'm not sure if I violated class C because my assumption was that I was a participating aircraft. Further; I followed the departure instructions as given. However; it was clearly not what the controller assumed would happen. In the confusion and the distraction of the controller conversation and situation; I may have violated class C either laterally or vertically.
Original NASA ASRS Text
Title: GA pilot reported entering BUR Class C airspace following departure from WHP.
Narrative: Departing VFR from KWHP. I had received a squawk code and informed tower of my request for flight following and my on course heading of 055. I'm not based at KWHP and not familiar with the local 'standard' procedures. On takeoff clearance from tower; the tower controller instructed me to make a left downwind departure. After takeoff; I initiated a left turn above 400 feet and within 1/2 mile of the airfield. I followed this with a turn to left downwind. Upon reaching midfield left downwind; I turned right out of traffic to a 030 heading. Shortly thereafter the controller came on the radio and yelled that I was entering Burbank airspace and was a traffic conflict. He then yelled at me that I was supposed to do the left downwind departure. I informed the controller that I did in fact fly to left downwind midfield then turned out of traffic. He responded with a lecture on if I'm not local familiar; that I need to inform him and how I am a conflict to traffic going into Burbank airspace; but no traffic call was given. I'm not a local based aircraft. I just flew in 45 minutes prior and at that time informed him that I'm not familiar. He continued to tell me that I was supposed to continue left downwind until he told me otherwise. These instructions were not given in the takeoff clearance. I responded saying that 'I will turn back toward the airfield to downwind' he responded 'no' but did not give any further direction or traffic calls. A long silence from the controller followed. I picked up a visual on a business jet on final into Burbank; stopped my climb and maintained visual separation. Upon us passing; he said; do you have a visual on the [traffic]? I responded affirmative. Following this the controller then lectured me again of what he expected me to do. I informed the controller; 'My mistake; I flew to left downwind then departed the pattern from midfield; I was under the impression that was the departure instruction.' The controller then responded with; 'you are correct it is your mistake; see what your mistake almost caused.' Following this a hand off to Approach occurred.In the misunderstanding of the departure; based off the squawk code and the discussion of on course heading it was my assumption that I was now a Class C participant. I'm not sure if I violated Class C because my assumption was that I was a participating aircraft. Further; I followed the departure instructions as given. However; it was clearly not what the controller assumed would happen. In the confusion and the distraction of the controller conversation and situation; I may have violated Class C either laterally or vertically.
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.