37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1404099 |
Time | |
Date | 201611 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR EMZOH 3 |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 10000 Flight Crew Type 1000 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Other / Unknown |
Narrative:
On the EMZOH3 STAR into oak; I noticed the mandatory altitudes on the arrival; from the mynee fix inbound were below the sfo class B airspace; yet there were no mandatory airspeeds listed on the EMZOH3 STAR. Although oak is a secondary airport into the sfo area; it still has a class B airspace chart for sfo; but none of the arrival fixes are listed on that chart. This forces us to go to the low level enroute chart; zoom in until the class B 'wedding cake' is displayed; then go back and forth between that chart and the STAR chart; to see which waypoints might be below the floor of the class B. I believe this causes a lot of extra work in the enroute/arrival environment that could easily be avoided if all the stars that enter or fall below class B would have associated mandatory speeds and or verbiage telling crews specifically which waypoints are below class B if flown as a 'descent via' arrival. This is not an koak only problem; I have also seen it flying into ksjc; kbfi; ksna; kont; kdfw and places in the northeast USA. I have often been advised by ATC in the ny area that 'you are leaving class B airspace' which helps with speed planning to some degree; as long as you know if you are completely exiting class B and not just exiting one area to now be below another part of the same class B. Also keep in mind; they only tell you that you are leaving if you were already in it; if you are simply being vectored under it; there is no notification. In short; please update any STAR with speeds that comply with the class B requirements by either having mandatory speeds or a note stating aircraft must fly no faster than clean maneuvering speed at the affected waypoints.
Original NASA ASRS Text
Title: B757 Captain lamented the lack of any indication on arrival charts of where an aircraft landing at a secondary airport will pass below or arrive below the Class B veil; requiring a 200 knot speed restriction.
Narrative: On the EMZOH3 STAR into OAK; I noticed the mandatory altitudes on the arrival; from the MYNEE fix inbound were below the SFO Class B airspace; yet there were no mandatory airspeeds listed on the EMZOH3 STAR. Although OAK is a secondary airport into the SFO area; it still has a CLASS B Airspace chart for SFO; but none of the arrival fixes are listed on that chart. This forces us to go to the low level enroute chart; zoom in until the CLASS B 'Wedding cake' is displayed; then go back and forth between that chart and the STAR chart; to see which waypoints might be below the floor of the CLASS B. I believe this causes a lot of extra work in the enroute/arrival environment that could easily be avoided if ALL the STARs that enter or fall below CLASS B would have associated mandatory speeds and or verbiage telling crews specifically which waypoints are below CLASS B if flown as a 'Descent Via' arrival. This is not an KOAK only problem; I have also seen it flying into KSJC; KBFI; KSNA; KONT; KDFW and places in the NE USA. I have often been advised by ATC in the NY area that 'You are leaving Class B airspace' which helps with speed planning to some degree; as long as you know if you are completely exiting CLASS B and not just exiting one area to now be below another part of the same CLASS B. Also keep in mind; they only tell you that you are leaving if you were already in it; if you are simply being vectored under it; there is no notification. In short; please update any STAR with speeds that comply with the CLASS B requirements by either having mandatory speeds or a note stating aircraft must fly no faster than Clean Maneuvering Speed at the affected waypoints.
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.