37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 391540 |
Time | |
Date | 199801 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : lga |
State Reference | NY |
Altitude | agl bound lower : 0 agl bound upper : 50 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : lga |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent : approach landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : commercial pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 24000 flight time type : 2500 |
ASRS Report | 391540 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 230 flight time total : 16000 flight time type : 4500 |
ASRS Report | 391537 |
Events | |
Anomaly | conflict : ground critical other anomaly other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : insufficient time |
Consequence | other Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Narrative:
I was the captain on MD80 flight from buf to lga on saturday morning jan/sat/98. I flew the approach and landing in visual conditions to runway 31. The approach and landing were made per pilot handbook procedures. The landing weight used to determine the approach speed was taken from the gross weight window on the fuel totalizer. The approach was stable and seemed normal until the flare. The flare was initiated at approximately 50 ft, but the aircraft responded sluggishly. We landed firmly, but it did not seem hard. A postflt walkaround by maintenance indicated a tailskid strike and some skin damage. I was surprised by the damage given that the landing was made from a stable approach with a sink rate of 700 FPM. If the flare did anything, it had to have decreased the sink rate below that. Aircraft certification requires transport category aircraft to be able to withstand -- without damage - - an impact of 600 FPM at full takeoff gross weight. We were nearly 20000 pounds under that. There was no sharp bump or strut bottoming feeling to the landing. The flight attendants on the aft jump seat didn't feel any tail strike. However, since the first officer stated that he did not notice the damage on his preflight walkaround, I assumed it was done on this landing, and wrote the aircraft up as having a possible hard landing. On review of my part of the flight, I realized that I had used a wrong gross weight for landing. Although I had estimated the landing weight based upon the gross weight read-out on the fuel totalizer, the read-out was wrong. The read-out is a window that displays the sum of the zero fuel weight and the remaining fuel. If an erroneous zero fuel weight is set into the totalizer, an erroneous gross weight will be displayed. Evidence suggests this is exactly what happened. One of the steps in the before takeoff checklist contains 2 important items. The first item is germane to the takeoff, the other to the landing. The step is titled 'takeoff data and zero fuel weight...set.' during this step the v-spds are set on the airspeed indicator and the proper zero fuel weight is set into the fuel totalizer. The v-spds are essential, but, at this point in the flight, a display showing total gross weight is not. Pilots are trained from day one to continuously sort and attach an appropriate priority to incoming information. Consequently, when one is sorting what is needed to make a takeoff, the importance of setting a zero fuel weight may diminish to nearly zero and a missed step is the result. I believe, this may have been what happened in the process of launching this early morning flight. We must have satisfied, at least in our minds, this step by setting the v-spds only. As a result, the zero fuel weight was never set properly. Two experienced pilots made the same error simultaneously. Therefore, I believe, this step should be split, for emphasis, into 2 steps. One for each item accomplished, each with its own response. But that is only part of the story. The speeds actually used and the speeds that should have been used were different by 8 KTS. Given the extra speed additives used, that speed difference should not have resulted in a hard landing and damage.
Original NASA ASRS Text
Title: HARD LNDG IN AN MD80 AFTER A HIGH FLARE. FLC CITES WRONG LNDG WT WITH AN 8 KT SPD DEFICIT.
Narrative: I WAS THE CAPT ON MD80 FLT FROM BUF TO LGA ON SATURDAY MORNING JAN/SAT/98. I FLEW THE APCH AND LNDG IN VISUAL CONDITIONS TO RWY 31. THE APCH AND LNDG WERE MADE PER PLT HANDBOOK PROCS. THE LNDG WT USED TO DETERMINE THE APCH SPD WAS TAKEN FROM THE GROSS WT WINDOW ON THE FUEL TOTALIZER. THE APCH WAS STABLE AND SEEMED NORMAL UNTIL THE FLARE. THE FLARE WAS INITIATED AT APPROX 50 FT, BUT THE ACFT RESPONDED SLUGGISHLY. WE LANDED FIRMLY, BUT IT DID NOT SEEM HARD. A POSTFLT WALKAROUND BY MAINT INDICATED A TAILSKID STRIKE AND SOME SKIN DAMAGE. I WAS SURPRISED BY THE DAMAGE GIVEN THAT THE LNDG WAS MADE FROM A STABLE APCH WITH A SINK RATE OF 700 FPM. IF THE FLARE DID ANYTHING, IT HAD TO HAVE DECREASED THE SINK RATE BELOW THAT. ACFT CERTIFICATION REQUIRES TRANSPORT CATEGORY ACFT TO BE ABLE TO WITHSTAND -- WITHOUT DAMAGE - - AN IMPACT OF 600 FPM AT FULL TKOF GROSS WT. WE WERE NEARLY 20000 LBS UNDER THAT. THERE WAS NO SHARP BUMP OR STRUT BOTTOMING FEELING TO THE LNDG. THE FLT ATTENDANTS ON THE AFT JUMP SEAT DIDN'T FEEL ANY TAIL STRIKE. HOWEVER, SINCE THE FO STATED THAT HE DID NOT NOTICE THE DAMAGE ON HIS PREFLT WALKAROUND, I ASSUMED IT WAS DONE ON THIS LNDG, AND WROTE THE ACFT UP AS HAVING A POSSIBLE HARD LNDG. ON REVIEW OF MY PART OF THE FLT, I REALIZED THAT I HAD USED A WRONG GROSS WT FOR LNDG. ALTHOUGH I HAD ESTIMATED THE LNDG WT BASED UPON THE GROSS WT READ-OUT ON THE FUEL TOTALIZER, THE READ-OUT WAS WRONG. THE READ-OUT IS A WINDOW THAT DISPLAYS THE SUM OF THE ZERO FUEL WT AND THE REMAINING FUEL. IF AN ERRONEOUS ZERO FUEL WT IS SET INTO THE TOTALIZER, AN ERRONEOUS GROSS WT WILL BE DISPLAYED. EVIDENCE SUGGESTS THIS IS EXACTLY WHAT HAPPENED. ONE OF THE STEPS IN THE BEFORE TKOF CHKLIST CONTAINS 2 IMPORTANT ITEMS. THE FIRST ITEM IS GERMANE TO THE TKOF, THE OTHER TO THE LNDG. THE STEP IS TITLED 'TKOF DATA AND ZERO FUEL WT...SET.' DURING THIS STEP THE V-SPDS ARE SET ON THE AIRSPD INDICATOR AND THE PROPER ZERO FUEL WT IS SET INTO THE FUEL TOTALIZER. THE V-SPDS ARE ESSENTIAL, BUT, AT THIS POINT IN THE FLT, A DISPLAY SHOWING TOTAL GROSS WT IS NOT. PLTS ARE TRAINED FROM DAY ONE TO CONTINUOUSLY SORT AND ATTACH AN APPROPRIATE PRIORITY TO INCOMING INFO. CONSEQUENTLY, WHEN ONE IS SORTING WHAT IS NEEDED TO MAKE A TKOF, THE IMPORTANCE OF SETTING A ZERO FUEL WT MAY DIMINISH TO NEARLY ZERO AND A MISSED STEP IS THE RESULT. I BELIEVE, THIS MAY HAVE BEEN WHAT HAPPENED IN THE PROCESS OF LAUNCHING THIS EARLY MORNING FLT. WE MUST HAVE SATISFIED, AT LEAST IN OUR MINDS, THIS STEP BY SETTING THE V-SPDS ONLY. AS A RESULT, THE ZERO FUEL WT WAS NEVER SET PROPERLY. TWO EXPERIENCED PLTS MADE THE SAME ERROR SIMULTANEOUSLY. THEREFORE, I BELIEVE, THIS STEP SHOULD BE SPLIT, FOR EMPHASIS, INTO 2 STEPS. ONE FOR EACH ITEM ACCOMPLISHED, EACH WITH ITS OWN RESPONSE. BUT THAT IS ONLY PART OF THE STORY. THE SPDS ACTUALLY USED AND THE SPDS THAT SHOULD HAVE BEEN USED WERE DIFFERENT BY 8 KTS. GIVEN THE EXTRA SPD ADDITIVES USED, THAT SPD DIFFERENCE SHOULD NOT HAVE RESULTED IN A HARD LNDG AND DAMAGE.
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.