An air carrier blows down a temporary chain link fence while xstarting its #2 engine after pushback.

Attributes
ACN	435600
Time
Date	199904
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : geg.airport
State Reference	WA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : geg.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	ground : parked ground : pushback
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : commercial pilot : atp pilot : multi engine
Experience	flight time last 90 days : 150 flight time total : 18000 flight time type : 6000
ASRS Report	435600
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Problem Areas	Flight Crew Human Performance Maintenance Human Performance Company Aircraft Airport
Primary Problem	Company

Narrative:

APU was inoperative, so per company procedures, 1 engine was started at the gate using air bottle. Aircraft was then pushed back for a xbleed start. All company procedures and checklists were used and followed. Both before pushback and before the tug was disconnected, the ramp crew was reminded a clear area was required behind the aircraft due to engine thrust required during the xbleed start operation. After accomplishing the xbleed start and all after-start checklists, we contacted ground control for taxi. At that time ground advised us that we had blown over 100-200 ft of chain link fence located 100 yards behind the aircraft. The fence was a temporary fence erected the day before, and not anchored or weighted. We were unaware of the hazard, and the fence was not on the NOTAM or the company field and facilities report. We contacted our operations, and requested that they advise the rampers of the problem so the situation would not be repeated.

Original NASA ASRS Text

Title: AN ACR BLOWS DOWN A TEMPORARY CHAIN LINK FENCE WHILE XSTARTING ITS #2 ENG AFTER PUSHBACK.

Narrative: APU WAS INOP, SO PER COMPANY PROCS, 1 ENG WAS STARTED AT THE GATE USING AIR BOTTLE. ACFT WAS THEN PUSHED BACK FOR A XBLEED START. ALL COMPANY PROCS AND CHKLISTS WERE USED AND FOLLOWED. BOTH BEFORE PUSHBACK AND BEFORE THE TUG WAS DISCONNECTED, THE RAMP CREW WAS REMINDED A CLR AREA WAS REQUIRED BEHIND THE ACFT DUE TO ENG THRUST REQUIRED DURING THE XBLEED START OP. AFTER ACCOMPLISHING THE XBLEED START AND ALL AFTER-START CHKLISTS, WE CONTACTED GND CTL FOR TAXI. AT THAT TIME GND ADVISED US THAT WE HAD BLOWN OVER 100-200 FT OF CHAIN LINK FENCE LOCATED 100 YARDS BEHIND THE ACFT. THE FENCE WAS A TEMPORARY FENCE ERECTED THE DAY BEFORE, AND NOT ANCHORED OR WEIGHTED. WE WERE UNAWARE OF THE HAZARD, AND THE FENCE WAS NOT ON THE NOTAM OR THE COMPANY FIELD AND FACILITIES RPT. WE CONTACTED OUR OPS, AND REQUESTED THAT THEY ADVISE THE RAMPERS OF THE PROB SO THE SIT WOULD NOT BE REPEATED.

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.