Mdt crew had a smoking gpu plug.

Attributes
ACN	495917
Time
Date	200012
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	agl single value : 0
Environment
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Transport, High Wing, 2 Turboprop Eng
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument pilot : multi engine pilot : private pilot : atp
Experience	flight time last 90 days : 190 flight time total : 1700 flight time type : 190
ASRS Report	495917
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Events
Anomaly	aircraft equipment problem : critical other anomaly other anomaly other anomaly other
Independent Detector	other other : 3
Resolutory Action	none taken : detected after the fact other
Consequence	other
Supplementary
Problem Areas	Aircraft
Primary Problem	Aircraft

Narrative:

During engine start, ramper noticed smoke coming from gpu plus into aircraft. He indicated this to us after disconnecting plug. We shut down engines, performed on ground emergency memory items, and evacuate/evacuationed aircraft. No injuries or aircraft damage resulted. Gpu was found faulty. It was awkward reacting to the situation because we did not know exactly what the problem was. We took it as a worst case scenario and evacuate/evacuationed. Ramper was assertive in communicating there was a problem.

Original NASA ASRS Text

Title: MDT CREW HAD A SMOKING GPU PLUG.

Narrative: DURING ENG START, RAMPER NOTICED SMOKE COMING FROM GPU PLUS INTO ACFT. HE INDICATED THIS TO US AFTER DISCONNECTING PLUG. WE SHUT DOWN ENGS, PERFORMED ON GND EMER MEMORY ITEMS, AND EVACED ACFT. NO INJURIES OR ACFT DAMAGE RESULTED. GPU WAS FOUND FAULTY. IT WAS AWKWARD REACTING TO THE SIT BECAUSE WE DID NOT KNOW EXACTLY WHAT THE PROB WAS. WE TOOK IT AS A WORST CASE SCENARIO AND EVACED. RAMPER WAS ASSERTIVE IN COMMUNICATING THERE WAS A PROB.

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.