Narrative:

Approached the 5;000 base section of the seattle class B; student was supposed to begin the descent to avoid the airspace and continue direct to bfi. I looked at the moving map 530WAAS with current navigation chip; and crosschecked the altitude and realized the student failed to start down. I immediately took control of the aircraft and made an immediate left 180 to return to the 6;000 foot floor airspace. Upon examining the track on our portable garmin 496 it appears we made a 0.3nm incursion into the airspace.I typically use the garmin 496 for weather and basic terrain orientation since the database is out of date. The problem with the out of date database; it shows incorrect sector altitude with base of class B at 6;000. This may have contributed to the confusion. Remainder of flight continued normally to bfi. No traffic conflict was observed or reported. Contributing factor is configuration of the class B airspace.

Google
 

Original NASA ASRS Text

Title: A BE36 instructor with student reported an inadvertent entry into SEA Class B; possibly due to the student using a Garmin 496 with an out of date database. A 530WAAS correctly showed the Class B floor had lowered since the 496 was last updated. An immediate 180 degree turn was initiated.

Narrative: Approached the 5;000 base section of the Seattle class B; Student was supposed to begin the descent to avoid the airspace and continue direct to BFI. I looked at the moving map 530WAAS with current navigation chip; and crosschecked the altitude and realized the student failed to start down. I immediately took control of the aircraft and made an immediate left 180 to return to the 6;000 foot floor airspace. Upon examining the track on our portable Garmin 496 it appears we made a 0.3nm incursion into the airspace.I typically use the Garmin 496 for weather and basic terrain orientation since the database is out of date. The problem with the out of date database; it shows incorrect sector altitude with base of class B at 6;000. This may have contributed to the confusion. Remainder of flight continued normally to BFI. No traffic conflict was observed or reported. Contributing factor is configuration of the Class B airspace.

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.