A C172 pilot taxied past the runway 6 hold line at bmg.

Attributes
ACN	746764
Time
Date	200707
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bmg.airport
State Reference	IN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	company : corporate
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 33 flight time total : 464 flight time type : 306
ASRS Report	746764
Events
Anomaly	incursion : runway
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Airport Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was 'cleared to taxi to runway 6' at bmg. I taxied from the GA ramp via taxiway A4; sbound on taxiway a to taxiway B. I reconfirmed my taxi clearance with bmg ground upon reaching the intersection of txwys a and B; then taxied wbound to runway 6 via taxiway B; crossing runway 35/17. Upon reaching taxiway B3 on the approach end of runway 6; I did not see a runway boundary hold short line. There is a displaced threshold (I had my airport diagram at the ready); so I completed my run-up at taxiway B3 and called ready for takeoff. During climb out I noticed a hold short line on taxiway B between taxiway B2 and taxiway B3 -- ahead of the indicated run-up area adjacent to an unmarked taxiway. Upon reviewing a satellite photograph of the runway/taxiway confign at the approach end of runway 6; I now understand that I mistakenly crossed the holding position/runway boundary for runway 6. ATC did not mention an incursion. Contributing factors included dissimilar markings between txwys B2 and B3 and an airport diagram that suggest a run-up pad area at the approach end of runway 6 that is incorrectly portrayed in the us terminal procedures volume. Additional factors included my being unfamiliar with the airport confign; failure to confirm hold short line with ATC and an expectation that the runway 6 run-up pad confign would be similar to runway 35/17.

Original NASA ASRS Text

Title: A C172 PLT TAXIED PAST THE RWY 6 HOLD LINE AT BMG.

Narrative: I WAS 'CLRED TO TAXI TO RWY 6' AT BMG. I TAXIED FROM THE GA RAMP VIA TXWY A4; SBOUND ON TXWY A TO TXWY B. I RECONFIRMED MY TAXI CLRNC WITH BMG GND UPON REACHING THE INTXN OF TXWYS A AND B; THEN TAXIED WBOUND TO RWY 6 VIA TXWY B; XING RWY 35/17. UPON REACHING TXWY B3 ON THE APCH END OF RWY 6; I DID NOT SEE A RWY BOUNDARY HOLD SHORT LINE. THERE IS A DISPLACED THRESHOLD (I HAD MY ARPT DIAGRAM AT THE READY); SO I COMPLETED MY RUN-UP AT TXWY B3 AND CALLED READY FOR TKOF. DURING CLBOUT I NOTICED A HOLD SHORT LINE ON TXWY B BTWN TXWY B2 AND TXWY B3 -- AHEAD OF THE INDICATED RUN-UP AREA ADJACENT TO AN UNMARKED TXWY. UPON REVIEWING A SATELLITE PHOTOGRAPH OF THE RWY/TXWY CONFIGN AT THE APCH END OF RWY 6; I NOW UNDERSTAND THAT I MISTAKENLY CROSSED THE HOLDING POS/RWY BOUNDARY FOR RWY 6. ATC DID NOT MENTION AN INCURSION. CONTRIBUTING FACTORS INCLUDED DISSIMILAR MARKINGS BTWN TXWYS B2 AND B3 AND AN ARPT DIAGRAM THAT SUGGEST A RUN-UP PAD AREA AT THE APCH END OF RWY 6 THAT IS INCORRECTLY PORTRAYED IN THE US TERMINAL PROCS VOLUME. ADDITIONAL FACTORS INCLUDED MY BEING UNFAMILIAR WITH THE ARPT CONFIGN; FAILURE TO CONFIRM HOLD SHORT LINE WITH ATC AND AN EXPECTATION THAT THE RWY 6 RUN-UP PAD CONFIGN WOULD BE SIMILAR TO RWY 35/17.

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