B767 ingests self induced FOD during xbleed start.

Attributes
ACN	716189
Time
Date	200611
Place
Locale Reference	airport : rsw.airport
State Reference	FL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B767 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : pushback
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : atp pilot : cfi pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 15000 flight time type : 6000
ASRS Report	716189
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	ground encounters : fod ground encounters : vehicle
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	other
Supplementary
Problem Areas	Aircraft Company Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

APU was MEL'ed inoperative. Right engine was started at the gate and we pushed back after start. When brakes were set for disconnect I asked the tug driver if it was clear and if there was room behind aircraft to make a xbleed start. He said yes. First officer called ground to check if clear behind aircraft for the xbleed start. Ground control said it was clear. We had a 10 KT tailwind up the engine tailpipe which caused a longer start time to stabilize the engine. I pushed up the right engine for more duct pressure to start the left engine. A tug passed behind aircraft during start and a cargo can was blown over. The trash inside the can was blown around and a black plastic bag was sucked into the right engine. We felt a shudder with no egt rise and we shut down right engine for FOD. After taxi back to gate; maintenance found some black plastic and newspaper stuck in the right engine which he removed. A test run on the right engine was normal and the logbook was signed off. No further problems occurred on the flight from rsw. Even though care was used to clear behind aircraft; a lot of uncontrolled traffic moves around the airplanes. Noise can be missed with all this activity. Caution should be used when aircraft are starting or being moved.

Original NASA ASRS Text

Title: B767 INGESTS SELF INDUCED FOD DURING XBLEED START.

Narrative: APU WAS MEL'ED INOP. R ENG WAS STARTED AT THE GATE AND WE PUSHED BACK AFTER START. WHEN BRAKES WERE SET FOR DISCONNECT I ASKED THE TUG DRIVER IF IT WAS CLR AND IF THERE WAS ROOM BEHIND ACFT TO MAKE A XBLEED START. HE SAID YES. FO CALLED GND TO CHK IF CLR BEHIND ACFT FOR THE XBLEED START. GND CTL SAID IT WAS CLR. WE HAD A 10 KT TAILWIND UP THE ENG TAILPIPE WHICH CAUSED A LONGER START TIME TO STABILIZE THE ENG. I PUSHED UP THE R ENG FOR MORE DUCT PRESSURE TO START THE L ENG. A TUG PASSED BEHIND ACFT DURING START AND A CARGO CAN WAS BLOWN OVER. THE TRASH INSIDE THE CAN WAS BLOWN AROUND AND A BLACK PLASTIC BAG WAS SUCKED INTO THE R ENG. WE FELT A SHUDDER WITH NO EGT RISE AND WE SHUT DOWN R ENG FOR FOD. AFTER TAXI BACK TO GATE; MAINT FOUND SOME BLACK PLASTIC AND NEWSPAPER STUCK IN THE R ENG WHICH HE REMOVED. A TEST RUN ON THE R ENG WAS NORMAL AND THE LOGBOOK WAS SIGNED OFF. NO FURTHER PROBS OCCURRED ON THE FLT FROM RSW. EVEN THOUGH CARE WAS USED TO CLR BEHIND ACFT; A LOT OF UNCTLED TFC MOVES AROUND THE AIRPLANES. NOISE CAN BE MISSED WITH ALL THIS ACTIVITY. CAUTION SHOULD BE USED WHEN ACFT ARE STARTING OR BEING MOVED.

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.