PA34 pilot exiting the runway missed his assigned taxiway and taxied onto the grass.

Attributes
ACN	631792
Time
Date	200409
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lan.airport
State Reference	MI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : lan.tower
Operator	general aviation : personal
Make Model Name	PA-34-200 Seneca I
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi landing : roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : lan.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Flight Phase	landing : go around
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : atp
Experience	flight time last 90 days : 43 flight time total : 2787 flight time type : 1096
ASRS Report	631793
Person 2
Affiliation	government : faa
Function	controller : local
Events
Anomaly	excursion : runway
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

After landing on runway 28L at lan I missed the taxiway turnoff and taxied into the grass on the south side of the runway. This caused an air carrier to go around. No damage was done to my plane. I tried to turn off on taxiway M but got confused by the blue lights and turned off between taxiway D and M, onto the grass. I should have noticed there was no yellow lead-in line to a taxiway at that point. Callback conversation with reporter revealed the following information: the pilot stated that there were no consequences to his runway excursion except for making an air carrier go around as he taxied back onto the runway. He said controllers didn't react or respond to his event. When I asked him if there was any kind of FAA investigation, he said no but the airport police came to his aircraft, inspected it for damage and questioned him about his sobriety and well-being. He could not get a clearance back to his home base until the police completed their inspection and quesitoning. The airport maintenance crew also inspected the runway for possible aircraft parts. He has not heard from the FAA or any auths about this incident.

Original NASA ASRS Text

Title: PA34 PLT EXITING THE RWY MISSED HIS ASSIGNED TXWY AND TAXIED ONTO THE GRASS.

Narrative: AFTER LNDG ON RWY 28L AT LAN I MISSED THE TXWY TURNOFF AND TAXIED INTO THE GRASS ON THE S SIDE OF THE RWY. THIS CAUSED AN ACR TO GO AROUND. NO DAMAGE WAS DONE TO MY PLANE. I TRIED TO TURN OFF ON TXWY M BUT GOT CONFUSED BY THE BLUE LIGHTS AND TURNED OFF BTWN TXWY D AND M, ONTO THE GRASS. I SHOULD HAVE NOTICED THERE WAS NO YELLOW LEAD-IN LINE TO A TXWY AT THAT POINT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE PLT STATED THAT THERE WERE NO CONSEQUENCES TO HIS RWY EXCURSION EXCEPT FOR MAKING AN ACR GO AROUND AS HE TAXIED BACK ONTO THE RWY. HE SAID CTLRS DIDN'T REACT OR RESPOND TO HIS EVENT. WHEN I ASKED HIM IF THERE WAS ANY KIND OF FAA INVESTIGATION, HE SAID NO BUT THE ARPT POLICE CAME TO HIS ACFT, INSPECTED IT FOR DAMAGE AND QUESTIONED HIM ABOUT HIS SOBRIETY AND WELL-BEING. HE COULD NOT GET A CLRNC BACK TO HIS HOME BASE UNTIL THE POLICE COMPLETED THEIR INSPECTION AND QUESITONING. THE ARPT MAINT CREW ALSO INSPECTED THE RWY FOR POSSIBLE ACFT PARTS. HE HAS NOT HEARD FROM THE FAA OR ANY AUTHS ABOUT THIS INCIDENT.

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.