2 engine air carrier large transport tail strike on takeoff.

Attributes
ACN	143987
Time
Date	199005
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sna
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 153 flight time total : 18420 flight time type : 1461
ASRS Report	143987
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 190 flight time total : 6800 flight time type : 275
ASRS Report	143988
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	procedure or policy : unspecified

Narrative:

Noise abatement departure at orange county. At liftoff felt a bump. It was a normal rotation and liftoff. Upon arrival at dfw we were surprised that the tail had struck the runway. We had thoroughly briefed the departure and had, as far as we knew, followed procedures. Perhaps these procedures need review. After the departure I contacted our maintenance department, then our dispatcher. The dispatcher contacted the tower and our technical maintenance people. He relayed to me that the tower thought the departure was normal and our technical people felt that if the aircraft was handling normally and pressurization was normal, they felt I could continue to my destination. With that input and with my determination that the aircraft seemed normal, I proceeded to destination. The dispatcher also had said that if they found out anything else, he would contact me. I had no further contact with him and only found out we had a tail strike upon arrival. Supplemental information from acn 143988: apparently this aircraft type, coupled with sna noise procedures, is candidate for tail strike. Perhaps sna noise procedure should be reviewed, and the aircraft type susceptibility to tail strike.

Original NASA ASRS Text

Title: 2 ENGINE ACR LGT TAIL STRIKE ON TKOF.

Narrative: NOISE ABATEMENT DEP AT ORANGE COUNTY. AT LIFTOFF FELT A BUMP. IT WAS A NORMAL ROTATION AND LIFTOFF. UPON ARR AT DFW WE WERE SURPRISED THAT THE TAIL HAD STRUCK THE RWY. WE HAD THOROUGHLY BRIEFED THE DEP AND HAD, AS FAR AS WE KNEW, FOLLOWED PROCS. PERHAPS THESE PROCS NEED REVIEW. AFTER THE DEP I CONTACTED OUR MAINT DEPT, THEN OUR DISPATCHER. THE DISPATCHER CONTACTED THE TWR AND OUR TECHNICAL MAINT PEOPLE. HE RELAYED TO ME THAT THE TWR THOUGHT THE DEP WAS NORMAL AND OUR TECHNICAL PEOPLE FELT THAT IF THE ACFT WAS HANDLING NORMALLY AND PRESSURIZATION WAS NORMAL, THEY FELT I COULD CONTINUE TO MY DEST. WITH THAT INPUT AND WITH MY DETERMINATION THAT THE ACFT SEEMED NORMAL, I PROCEEDED TO DEST. THE DISPATCHER ALSO HAD SAID THAT IF THEY FOUND OUT ANYTHING ELSE, HE WOULD CONTACT ME. I HAD NO FURTHER CONTACT WITH HIM AND ONLY FOUND OUT WE HAD A TAIL STRIKE UPON ARR. SUPPLEMENTAL INFO FROM ACN 143988: APPARENTLY THIS ACFT TYPE, COUPLED WITH SNA NOISE PROCS, IS CANDIDATE FOR TAIL STRIKE. PERHAPS SNA NOISE PROC SHOULD BE REVIEWED, AND THE ACFT TYPE SUSCEPTIBILITY TO TAIL STRIKE.

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.