37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1482920 |
Time | |
Date | 201709 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Military |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Component | |
Aircraft Component | Fuel Storage System |
Person 1 | |
Function | Check Pilot |
Qualification | Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 64 Flight Crew Total 2900 Flight Crew Type 2800 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance Inflight Event / Encounter Fuel Issue |
Narrative:
During aerial refueling (a/right); our augmented crew (composed of an extra pilot and an extra navigator) noticed the incremental fuel onloads passed by the tanker were not matching the planned gross weight of our aircraft given the fuel taken from the tanker at each increment. The navigator recalculated the fuel in the totalizer and checked it against the planned gross weight for that fuel quantity and noticed a discrepancy. The crew was not able to identify the source of the error and elected to continue taking fuel required for the remaining mission. The tanker crew was sympathetic to our fuel requirement and passed us an additional 10;400 pounds for a total of approximately 91;400 pounds of jaa. The pilot flying noted shortly after completing the post a/right checklist that the aircraft was sluggish in its handling. After thinking about the disparity in the numbers for another 10 minutes; the crew reached the conclusion that the basic aircraft weight was entered into the aircraft performance computer incorrectly. Upon closer examination; the actual number and the entered number differed by 20;000 pounds; making the performance computer think that the aircraft was 20;000 pounds lighter than it actually was. As a result; the extra fuel taken from the tanker resulted in the crew exceeding the published aircraft gross weight listed in the aircraft's technical order and caused a potentially dangerous situation. The crew then contacted our dispatcher (operations supervisor) for assistance while keeping the aircraft in smooth air and at 1 G. The dispatcher contacted base maintenance; depot engineers; manufacturer engineers; and the depot test pilot all for input; assistance; and guidance. The consensus was that our aircraft limit was predicated on a 2 G increment and that since the aircraft did not experience turbulence or exceed 1 G; the structure of the aircraft was fine and there was no structural event to worry about. In fact; the consensus from all parties; now including unit leadership; was that we could elect to continue the entire planned mission; including a subsequent a/right should the crew choose. At this point; the crew elected to decline the second aerial refueling and accomplish as much of the mission with the fuel we had in order to return to base within a comfortable fuel margin.in the future; the navigator (or another crew member) should verify the basic aircraft weight variable entered into the aircraft's performance computer during preflight. In this situation; the copilot accomplishes this task while the left-seat pilot accomplishes the exterior walk-around. The navigator would be the obvious choice to verify this data. In this case; the navigator elected to enter the weight and balance information but did not verify the basic aircraft weight entry made previously by the copilot. Again; in this case; the basic aircraft weight had already been entered into the apc by the copilot (indicated by a color change in the entry field from yellow to green) and the aircraft weight and balance data publication was sitting on the navigator's table. Given these two pieces of information; the navigator assumed that the data had been entered and verified against the aircraft weight and balance data publication. In hindsight; this would have been the easiest link in the chain to break.
Original NASA ASRS Text
Title: A Navigator of a military aircraft reported that due to a miscalculation of aircraft weight; they received an excessive amount of fuel from the tanker aircraft.
Narrative: During aerial refueling (A/R); our augmented crew (composed of an extra pilot and an extra navigator) noticed the incremental fuel onloads passed by the tanker were not matching the planned gross weight of our aircraft given the fuel taken from the tanker at each increment. The navigator recalculated the fuel in the totalizer and checked it against the planned gross weight for that fuel quantity and noticed a discrepancy. The crew was not able to identify the source of the error and elected to continue taking fuel required for the remaining mission. The tanker crew was sympathetic to our fuel requirement and passed us an additional 10;400 pounds for a total of approximately 91;400 pounds of JAA. The pilot flying noted shortly after completing the post A/R checklist that the aircraft was sluggish in its handling. After thinking about the disparity in the numbers for another 10 minutes; the crew reached the conclusion that the basic aircraft weight was entered into the aircraft performance computer incorrectly. Upon closer examination; the actual number and the entered number differed by 20;000 pounds; making the performance computer think that the aircraft was 20;000 pounds lighter than it actually was. As a result; the extra fuel taken from the tanker resulted in the crew exceeding the published aircraft gross weight listed in the aircraft's technical order and caused a potentially dangerous situation. The crew then contacted our dispatcher (Operations Supervisor) for assistance while keeping the aircraft in smooth air and at 1 G. The dispatcher contacted base maintenance; depot engineers; manufacturer engineers; and the depot test pilot all for input; assistance; and guidance. The consensus was that our aircraft limit was predicated on a 2 G increment and that since the aircraft did not experience turbulence or exceed 1 G; the structure of the aircraft was fine and there was no structural event to worry about. In fact; the consensus from all parties; now including unit leadership; was that we could elect to continue the entire planned mission; including a subsequent A/R should the crew choose. At this point; the crew elected to decline the second aerial refueling and accomplish as much of the mission with the fuel we had in order to return to base within a comfortable fuel margin.In the future; the navigator (or another crew member) should verify the basic aircraft weight variable entered into the aircraft's performance computer during preflight. In this situation; the copilot accomplishes this task while the left-seat pilot accomplishes the exterior walk-around. The navigator would be the obvious choice to verify this data. In this case; the navigator elected to enter the weight and balance information but did not verify the basic aircraft weight entry made previously by the copilot. Again; in this case; the basic aircraft weight had already been entered into the APC by the copilot (indicated by a color change in the entry field from yellow to green) and the aircraft weight and balance data publication was sitting on the navigator's table. Given these two pieces of information; the navigator assumed that the data had been entered and verified against the aircraft weight and balance data publication. In hindsight; this would have been the easiest link in the chain to break.
Data retrieved from NASA's ASRS site 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.