 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier pilot reported the EMZOH3 STAR to oak published speed is above the speed limit for being underneath the sfo class B airspace.
| Attributes | |
| ACN | 1686679 |
| Time | |
| Date | 201909 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | NCT.TRACON |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR EMZOH3 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 405 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Procedural FAR Deviation - Speed All Types |
Narrative:
We noted the EMZOH3 STAR places the aircraft below the san francisco class B airspace. It does not indicate this airspace; and the aircraft's flight management system does not take the associated speed limit into account (the legs page displays the normal 240 knot speed at mynee and later fixes). We programmed the required 200 knot speed; but recommend this should be coded into the arrival. A busy crew could easily miss the specific altitudes of the class B shelf. On a previous flight; the pilot with whom I was flying said he was slowing to comply with this requirement; and the captain said '...I've never had a problem with the class B before;' indicating that he didn't agree with the deceleration; and that the first officer should have maintained 250 knots. I recommend charting improvements to indicate class B airspace on STAR. This arrival places aircraft below class B.we could address this via bulletins; but I believe these are not permanent solutions. A note on the station page would be more effective (and currently exists); but publishing (and coding) the relevant speed would be best; in my opinion.
Original NASA ASRS Text
Title: An air carrier pilot reported the EMZOH3 STAR to OAK published speed is above the speed limit for being underneath the SFO Class B airspace.
Narrative: We noted the EMZOH3 STAR places the aircraft below the San Francisco Class B airspace. It does not indicate this airspace; and the aircraft's flight management system does not take the associated speed limit into account (the Legs page displays the normal 240 knot speed at MYNEE and later fixes). We programmed the required 200 knot speed; but recommend this should be coded into the arrival. A busy crew could easily miss the specific altitudes of the Class B shelf. On a previous flight; the pilot with whom I was flying said he was slowing to comply with this requirement; and the Captain said '...I've never had a problem with the Class B before;' indicating that he didn't agree with the deceleration; and that the first officer should have maintained 250 knots. I recommend charting improvements to indicate Class B airspace on STAR. This arrival places aircraft below Class B.We could address this via bulletins; but I believe these are not permanent solutions. A note on the station page would be more effective (and currently exists); but publishing (and coding) the relevant speed would be best; in my opinion.
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.