37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1368049 |
Time | |
Date | 201606 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SFB.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Sierra 24 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 22 Flight Crew Total 17000 Flight Crew Type 300 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance |
Narrative:
Inbound to sfb from the west and under radar vectors from orlando ATC under the class B but into class C airspace of sfb for a rwy 27L full stop approach/landing. Final controller instruction was to enter the mid field left downwind for runway 27L at sfb from a controller issued heading of 090 degrees. At this point I was about 2-3 nm from the downwind of the runway and I made a left turn followed by an immediate mid field right turn to enter the left downwind.next instruction was to change to tower freq of 135.25 for 27L. Tower controlled admonished me that I should have contacted the tower as I was in the pattern and caused a traffic conflict. Tower said my entry was not the correct lake jessup VFR arrival path. I replied I was not issued the VFR lake jessup arrival but on heading/vectors from orl approach. Tower controller told me not to do that again but to contact the tower prior to entering their pattern. After that I was cleared to land on 27L. I acknowledged and landed.in the future for sfb ops I will always request the published VFR arrival from the orlando radar controller for landing. Sfb is a very busy general aviation flight school training airport. No more radar vectors but other than to join the published arrival; I will request the VFR arrival even if there is no traffic. I can visually commence the published arrival with the proper altitude and comply with the arrival.
Original NASA ASRS Text
Title: Beech 24 pilot reported issues with ATC instructions for a VFR entry into SFB.
Narrative: Inbound to SFB from the west and under radar vectors from Orlando ATC under the Class B but into Class C airspace of SFB for a Rwy 27L full stop approach/landing. Final controller instruction was to enter the mid field left downwind for Runway 27L at SFB from a controller issued heading of 090 degrees. At this point I was about 2-3 nm from the downwind of the runway and I made a left turn followed by an immediate mid field right turn to enter the left downwind.Next instruction was to change to tower freq of 135.25 for 27L. Tower controlled admonished me that I should have contacted the tower as I was in the pattern and caused a traffic conflict. Tower said my entry was not the correct Lake Jessup VFR arrival path. I replied I was not issued the VFR Lake Jessup arrival but on heading/vectors from ORL approach. Tower controller told me not to do that again but to contact the tower prior to entering their pattern. After that I was cleared to land on 27L. I acknowledged and landed.In the future for SFB ops I will always request the published VFR arrival from the Orlando radar controller for landing. SFB is a very busy general aviation flight school training airport. No more radar vectors but other than to join the published arrival; I will request the VFR arrival even if there is no traffic. I can visually commence the published arrival with the proper altitude and comply with the arrival.
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.