 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
GA pilot reported the garmin navigation database was incorrect referencing the new sfo class B airspace.
| Attributes | |
| ACN | 1570622 |
| Time | |
| Date | 201808 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | NCT.TRACON |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Cruise |
| Route In Use | None |
| Flight Plan | None |
| Component | |
| Aircraft Component | Navigational Equipment and Processing |
| Person 1 | |
| Function | Single Pilot Pilot Flying |
| Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 35 Flight Crew Total 5200 Flight Crew Type 3500 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
I was taking a short trip to the coast from pao with a brand new garmin navigation database update into a brand new class B change for the sfo area. The new garmin update included the new class B inromation. The GPS showed me that the base of the class B changed from 4000 to 8000 not to far from osi VOR. This was a change; since it had been a shift from 4000 to 6000. I was briefly over 6000 before descending. When I returned; I double checked the new chart and found that the GPS data was wrong--the base was 6000 not 8000. I later checked with the also brand new database in the garmin receiver in my other airplane. It also showed incorrect information as to the base of the class B in that same area. It also showed 8000 instead of 6000.bottom line is that I relied on the newly downloaded database; which was supposed to accurately conform to the new changes in the class B. Although the new database in both airplanes seemed to conform to the many changes; it was inaccurate as to this area. This occurred only 2 days after the class B changes; so I am planning on informing garmin of their error. Both airplanes; with 2 separate garmin products; both with 2 new garmin database downloads were consistent but wrong.
Original NASA ASRS Text
Title: GA pilot reported the Garmin Navigation database was incorrect referencing the new SFO Class B airspace.
Narrative: I was taking a short trip to the coast from PAO with a brand new Garmin Navigation database update into a brand new Class B change for the SFO area. The new Garmin update included the new Class B inromation. The GPS showed me that the base of the Class B changed from 4000 to 8000 not to far from OSI VOR. This was a change; since it had been a shift from 4000 to 6000. I was briefly over 6000 before descending. When I returned; I double checked the new chart and found that the GPS data was wrong--the base was 6000 not 8000. I later checked with the also brand new database in the Garmin Receiver in my other airplane. It also showed incorrect information as to the base of the Class B in that same area. It also showed 8000 instead of 6000.Bottom line is that I relied on the newly downloaded database; which was supposed to accurately conform to the new changes in the Class B. Although the new database in both airplanes seemed to conform to the many changes; it was inaccurate as to this area. This occurred only 2 days after the Class B changes; so I am planning on informing Garmin of their error. Both airplanes; with 2 separate Garmin products; both with 2 new Garmin database downloads were consistent but wrong.
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.