Narrative:

At the time of the occurrence, I was accompanying a former student, now a private pilot, who had not been very active recently, and wanted me to ride along with her on the flight for reassurance and to establish currency. The plan called for a VFR departure from our home airport (N40) at 560 ft elevation, climb to 8500 ft to overfly the phl class B airspace and continue to our destination of kenmorr airpark in md (3w3). We departed the N40 airport and climbed to an indicated altitude of 7500 ft where we leveled off temporarily to avoid some scattered clouds above us. At about XA35, we would have crossed the lateral boundary, above the phl class B at a point about 5 NM west of the willow grove naval air station (knxx). After about 10 mins on our 245 degree heading, now about 12 NM northeast of ilg, we continued our climb, now able to avoid the clouds, to an indicated altitude of 8500 ft. At this point we decided to check the ATIS at bwi to see what the surface winds near our destination were doing. When we did so, we realized that our altimeter setting was high by 1000 ft. During the pre-takeoff check, not having a local altimeter setting, the altimeter is usually set to our field elevation of 560 ft. It was instead erroneously set 1000 ft high to 1560 ft. When we received the bwi altimeter setting we realized we had unknowingly penetrated the phl class B for approximately 10 mins or 25 NM. The error in setting the altimeter came primarily from the PF who was not current in aircraft and had mistakenly set it. I missed it as well. Scrutinizing the instrument setting on the ground would have avoided the error. Participating in VFR flight following from ATC, checking ATIS sooner, or conducting the flight under IFR, would have no doubt brought the error to our attention sooner. Next time we'll both be more diligent to avoid this type of error and read the instrument carefully on the ground.

Google
 

Original NASA ASRS Text

Title: AN INSTRUCTOR AND PRIVATE PLT, PRIOR TO TKOF, INCORRECTLY SET THE ALTIMETER OF THE BE35. THEY WERE FLYING 1000 FT HIGH. THE TRUE ALT WAS 1000 FT LOWER THAN INDICATED ON THE ALTIMETER.

Narrative: AT THE TIME OF THE OCCURRENCE, I WAS ACCOMPANYING A FORMER STUDENT, NOW A PVT PLT, WHO HAD NOT BEEN VERY ACTIVE RECENTLY, AND WANTED ME TO RIDE ALONG WITH HER ON THE FLT FOR REASSURANCE AND TO ESTABLISH CURRENCY. THE PLAN CALLED FOR A VFR DEP FROM OUR HOME ARPT (N40) AT 560 FT ELEVATION, CLB TO 8500 FT TO OVERFLY THE PHL CLASS B AIRSPACE AND CONTINUE TO OUR DEST OF KENMORR AIRPARK IN MD (3W3). WE DEPARTED THE N40 ARPT AND CLBED TO AN INDICATED ALT OF 7500 FT WHERE WE LEVELED OFF TEMPORARILY TO AVOID SOME SCATTERED CLOUDS ABOVE US. AT ABOUT XA35, WE WOULD HAVE CROSSED THE LATERAL BOUNDARY, ABOVE THE PHL CLASS B AT A POINT ABOUT 5 NM W OF THE WILLOW GROVE NAVAL AIR STATION (KNXX). AFTER ABOUT 10 MINS ON OUR 245 DEG HDG, NOW ABOUT 12 NM NE OF ILG, WE CONTINUED OUR CLB, NOW ABLE TO AVOID THE CLOUDS, TO AN INDICATED ALT OF 8500 FT. AT THIS POINT WE DECIDED TO CHK THE ATIS AT BWI TO SEE WHAT THE SURFACE WINDS NEAR OUR DEST WERE DOING. WHEN WE DID SO, WE REALIZED THAT OUR ALTIMETER SETTING WAS HIGH BY 1000 FT. DURING THE PRE-TKOF CHK, NOT HAVING A LCL ALTIMETER SETTING, THE ALTIMETER IS USUALLY SET TO OUR FIELD ELEVATION OF 560 FT. IT WAS INSTEAD ERRONEOUSLY SET 1000 FT HIGH TO 1560 FT. WHEN WE RECEIVED THE BWI ALTIMETER SETTING WE REALIZED WE HAD UNKNOWINGLY PENETRATED THE PHL CLASS B FOR APPROX 10 MINS OR 25 NM. THE ERROR IN SETTING THE ALTIMETER CAME PRIMARILY FROM THE PF WHO WAS NOT CURRENT IN ACFT AND HAD MISTAKENLY SET IT. I MISSED IT AS WELL. SCRUTINIZING THE INSTRUMENT SETTING ON THE GND WOULD HAVE AVOIDED THE ERROR. PARTICIPATING IN VFR FLT FOLLOWING FROM ATC, CHKING ATIS SOONER, OR CONDUCTING THE FLT UNDER IFR, WOULD HAVE NO DOUBT BROUGHT THE ERROR TO OUR ATTN SOONER. NEXT TIME WE'LL BOTH BE MORE DILIGENT TO AVOID THIS TYPE OF ERROR AND READ THE INSTRUMENT CAREFULLY ON THE GND.

Data retrieved from NASA's ASRS site as of July 2007 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.