CHI96FA342

NTSB accident investigation · Grumman F9F-2 · Kalamazoo, MI · September 19, 1996

Accident · Serious injuriesField investigationFinal report
Date
September 19, 1996, 17:21 local (21:21 UTC)
Place
Kalamazoo, MI
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
NX72WPGrumman F9F-2
Weather
Visual (VMC) · Day
Status
Completed · report June 5, 2000
Report
Approved by Office Director
Case key
15774

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The overrun of the runway as a result of the pilot's misjudgment of speed and distance because of an unreliable airspeed indication; reason for the unreliable airspeed indication was undetermined. Contributing to the accident was the pilot's perception of a power interruption and throttle/power control not being available for undetermined reasons.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine powerTakeoff
Miscellaneous,engine - surge
Airframe/component/system failure/malfunctionApproach - vfr pattern - downwind
Throttle/power control - not availablePilot in commandFactor
Reason for occurrence undetermined
Forced landingApproach - vfr pattern - downwind
Precautionary landing - initiatedPilot in command
Engine shutdown - performedPilot in command
OverrunLanding - roll
Flight/nav instruments,airspeed indicator - unreliable
Reason for occurrence undetermined
Airspeed - misjudgedPilot in commandCause
Distance - misjudgedPilot in commandCause
On ground/water encounter with terrain/waterLanding - roll
Terrain condition - berm
Object - fence

Analysis

According to the pilot, shortly after takeoff, about 200 feet above ground level, he felt a sudden deceleration and was thrown forward in his seat. He also noted that the airplane would not accelerate beyond 120 knots indicated airspeed, which he attributed to a problem with the pitot system, and that he decided to return to land. He said that while on the downwind leg, he retarded the throttle to idle, but the engine rpm reduced to 65 percent instead of the normal 28 percent. At this time, a red light illuminated in the cockpit, and the pilot stated that he believed this to be the warning light for the Emergency Fuel System. He said that as a precaution, he decided to shut the engine down and do a power-off landing. The pilot reported that he aimed for the first third to one-half-the-way down the runway, and he landed 'long and hot.' He was unable to stop on the remaining runway and steered the airplane on to a grassy area to the right side of the runway. He indicated that he had previously experienced anomalies with the fuel control unit and fuel pump; however, postaccident testing of these components did not reproduce the conditions reported by the pilot on the accident flight. Except for a slightly higher than normal idle (36 percent), the fuel controller performed satisfactorily. The airspeed indicator was damaged and could not be functionally tested.

Factual narrative

History of flight

On September 19, 1996, at 1721 eastern daylight time, a Grumman F9F-2, NX72WP, overran runway 35 during an emergency landing at the Kalamazoo/Battle Creek International Airport, Kalamazoo, Michigan. The pilot was seriously injured. The airplane was substantially damaged during its collision with a chainlink fence, ditch, road shoulder, berm, and the postlanding fire. Visual meteorological conditions prevailed, and the runway was dry at the time of the accident. The flight departed Kalamazoo about 1715 on a 14 Code of Federal Regulations Part 91 personal flight operating on an instrument flight rules flight plan.

During postaccident interviews, the pilot reported that the engine did not hesitate when he applied full power for the takeoff from runway 35. The pilot reported that the takeoff run and lift-off were normal for a hot day. He stated that about 200 feet above ground level (agl), he felt a sudden deceleration and was thrown forward in his seat. He stated that the airplane would not accelerate beyond 120 knots indicated airspeed (KIAS). Shortly after noting that the airspeed was not increasing, and thinking that an engine flameout was imminent, the pilot made a tight turn, continued to climb, and contacted the Federal Aviation Administration's (FAA) Air Traffic Control Tower (ATCT). He stated that he told the controller that he had a "problem" and wanted to return to Kalamazoo to land. The Kalamazoo ATCT transcript shows that the accident airplane was cleared for takeoff at 1715:58. At 1717:56, the pilot called the ATCT stating, "Whiskey Pops got a problem." The pilot told the ATCT that he was not certain what the problem was and that he intended to return to the airport. A few moments later the pilot said, "we'll stay in the pattern...normal pattern...seems as though we're not accelerating...it could be a problem with the pitot." The controller asked the pilot if he needed any assistance. The pilot replied, "Negative, we'll be all right, we're just...precautionary."

The pilot stated that the airspeed remained at 120 KIAS, but he sensed that the airplane was actually moving faster than 120 KIAS. The pilot stated that he flew the airplane to 2,000 feet above mean sea level (msl) in a left climbing turn to the downwind leg for runway 35. He stated that this altitude was a little higher than the normal traffic pattern for the airplane. While on the downwind leg, the pilot retarded the throttle to the idle stop. He stated that the rpm rolled back to about 65 percent instead of the normal 28 percent.

The pilot stated that during the downwind leg he recalled seeing a red light glowing on the left-hand console; however, he was unsure exactly when it illuminated. He stated that he believed that the red light was the Emergency Fuel System Warning Light. He stated that he did not manually switch on the emergency position fuel system. He stated that he knew that the emergency fuel system adds more fuel to the engine and that in the emergency mode rapid movement of the throttle could flame out the engine. Unable to obtain less than 65 percent rpm, and unsure of what the engine was going to do, the pilot stated that he shut down the engine to make a power-off landing.

According to FAA Form 8020-6, "Report of Aircraft Accident," at 1723, the wind direction and speed were 030 degrees magnetic at 6 knots. The pilot stated that he aimed for a point about one-third to one-half the way down runway 35 and that the airplane landed "long and hot." He stated that he retracted the flaps and applied the brakes after touchdown. The pilot stated that he observed obstacles at the end of the runway and to avoid them he put all of the pressure on the right toe-brake and steered the airplane onto the grassy area to the right side of the runway.

Witnesses

A witness at the fixed base operation on the airport's west side stated that he "first saw the aircraft west of the airport at...pattern altitude. The aircraft sounded and looked okay." He said that the airplane "banked from the downwind all the way around and came out on final just like all military landings. The airplane was going very fast and looked like it was going to be a high speed pass." A second witness, who was on Kilgore Road at the time of the accident-north of the airport-watched the airplane's landing roll. The police reported that the witness said he observed the accident airplane's wheels being cherry red during the landing roll as it neared the highway.

According to the ATCT controller statement, the accident airplane's ground speed was "220 knots on final approach...less than a mile from the runway." The controller also stated that the airplane touched down between taxiways B-2 and B-3 and "was going at a high rate of speed."

Personnel information

The pilot held an airline transport pilot certificate. In addition, the pilot held a "Statement of Acrobatic Competency" (FAA Form 8710-7) dated June 6, 1996, with the following maneuver limitations: "All Aerobatic Maneuvers Within AC Operations Limitations / Formation Non Aerobatic." The altitude limitations were "Level 3, 500 FT" and the authorized aircraft was listed as "F9F-2 Panther."

The pilot provided copies of his logbook that were directly related to the F9F-2 airplane to the investigator-in-charge (IIC). The logbook copies showed that he received 2 hours of dual instruction in a DeHavilland Vampire on September 25, 1985. He began flying the accident airplane on October 7, 1985. An entry in the pilot's logbook showed that he had received an "FAA Comp. Ck. 3 TO Ldgs" in the accident airplane on October 29, 1985. The pilot subsequently received Letters of Authorization (LOA) from the FAA to fly the F9F-2 airplane dated November 7, 1985; November 14, 1986; and October 20, 1987. A copy of the FAA Form 8710-7, a copy of the letter verifying the training in the DeHavilland Vampire, and a copy of the LOAs are appended to this report.

The logbook showed a total of 226.85 hours in the accident airplane. No other Grumman F9F-2 airplane flight times were shown. National Transportation Safety Board Form 6120 1/2, "Pilot/Operator Aircraft Accident Report," listed "236+" hours. In subsequent correspondence, the pilot indicated that he had a total of 333.4 hours in the accident airplane. According to the logbook, the pilot had flown the airplane 5.5 hours during June 1996. The last entry in the pilot's logbook was on June 8, 1996, which showed that the pilot had flown the accident airplane 1.5 hours and made three landings that day. Excerpts from the logbook are appended to this report.

Aircraft information

The accident airplane was a Korean War vintage military jet airplane.

The pilot provided copies of the airframe and powerplant logbooks to the IIC. According to the July 27, 1983, airframe logbook entry, NX72WP, serial number (S/N) 12078, was assembled "using new, spare, and surplus parts." The airplane received its special airworthiness certificate from the FAA on July 27, 1983. The logbook showed that the airplane had zero total time in service when it received the special airworthiness certificate.

The airframe logbook showed that the accident airplane's last annual inspection was completed on May 21, 1996, and that it had 373.4 hours on its Hobbs meter. There were no other logbook entries describing any airframe maintenance after the May 21st entry. The accident airplane's total airframe time, which is based on a review of the accident airplane's airframe logbook and the pilot's logbook copies, was 378.9 hours at the beginning of the accident flight.

According to a July 27, 1983, powerplant logbook entry, the accident airplane's Pratt and Whitney J42-P8 engine, S/N P400638, was "overhauled from new, spare, and surplus parts." This entry showed that the main fuel control unit (Bendix model TJ-Cl, S/N 17441) had been overhauled before installation

Aircraft

Registration
NX72WP
Reported as
Grumman F9F-2
Category
Airplane
Serial number
12078
Airframe hours
373
Engine
P&W J42P-8, 5,000 lbs thrust, turbo jet
Damage
Substantial damage
Fire
On-Ground
Flight
Personal · Part 91
Registered owner
Flying Warbirds Foundation
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · May 21, 1996 · 6 hours before
Departed
AZO · MI
Destination
Norfolk, VA
Flight plan
IFR
Airport
AZO · Kalamazoo/Battle Creek, runway 35, 6,499 × 150 ft, asphalt

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
52
Certificates
Commercial, Airline transport
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--no waivers/lim.
Seat
Center
Flight hours
2,323 total · 236 in this make and model · 2,236 as pilot in command · 12 in the last 90 days · 2 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
30° at 6 knots
Visibility
25 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 37 °F
Observed at
KAZ, 1 nm away

Docket · 174

The files NTSB released with the investigation on May 19, 2000, on NTSB’s docket system: statements, records, photos and specialists’ reports. 69.9 MB in all.

Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1Item 1 · .PDF · 822 KBSupplement CItem 2 · .PDF · 458 KBSupplement DItem 3 · .PDF · 529 KBAirport Diagram and Ground Scar LayoutItem 4 · .PDF · 128 KBStatements of InterviewItem 5 · .PDF · 672 KBFAA ATC ReportItem 6 · .PDF · 434 KBFAA PMI Observation Report of Fuel Pump Test RunItem 7 · .PDF · 121 KBInterview Statement by Kalamazoo, MI Dept. of Public SafetyItem 8 · .PDF · 123 KBFAA General Aviation Operations Inspector Handbook FAA 8700.1, ExcerptsItem 9 · .PDF · 842 KBCopies of Airframe and Engine LogbooksItem 10 · .PDF · 6.5 MBCorrespondence from Allied Signal EngineerItem 11 · .PDF · 470 KBCorrespondence from President of Aero TurbineItem 12 · .PDF · 294 KBMaintenance Documents - NX72WP's Fuel ControlItem 13 · .PDF · 12.2 MBExcerpts from Aircraft, Engine, and Fuel Control & Pump Maintenance ManualsItem 14 · .PDF · 3.0 MBInformation on Rolls Royce Nene EngineItem 15 · .PDF · 1.0 MBEngine Test Run ReportItem 16 · .PDF · 116 KBIllustration of F9F AirplaneItem 17 · .PDF · 144 KBCopy of Fuel Adjustment Instructions Given to Mechanic in Kalamazoo, MIItem 18 · .PDF · 73 KBMechanic Statement Who Adjusted Fuel Control on NX72WPItem 19 · .PDF · 262 KBNX72WP's Pilot-In-Command's Letter of AuthorizationItem 20 · .PDF · 187 KBNX72WP's Fuel Pumps (2) Test Report (Part 1)Item 21 · .PDF · 262 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 1)Item 22 · .PDF · 29 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 2)Item 23 · .PDF · 38 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 3)Item 24 · .PDF · 40 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 4)Item 25 · .PDF · 28 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 5)Item 26 · .PDF · 29 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 6)Item 27 · .PDF · 24 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 7)Item 28 · .PDF · 37 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 8)Item 29 · .PDF · 23 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 9)Item 30 · .PDF · 35 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 10)Item 31 · .PDF · 43 KBNX72WP's Fuel Pumps (2) Test Report (Part 2)Item 32 · .PDF · 187 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 1 to Part 2)Item 33 · .PDF · 51 KBNX72WP's Fuel Pumps (2) Test Report (Part 3)Item 34 · .PDF · 193 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 1 to Part 3)Item 35 · .PDF · 34 KBNX72WP's Fuel Pumps (2) Test Report (Attachment 2 to Part 3)Item 36 · .PDF · 39 KBFuel Control Test Run Report with NX72WP's Fuel Analysis (Part 1)Item 37 · .PDF · 277 KBFuel Control Test Run Report with NX72WP's Fuel Analysis (Part 2)Item 38 · .PDF · 326 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 1 to Part 2)Item 39 · .PDF · 32 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 2 to Part 2)Item 40 · .PDF · 40 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Part 3)Item 41 · .PDF · 121 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 1 to Part 3)Item 42 · .PDF · 51 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 2 to Part 3)Item 43 · .PDF · 28 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 3 to Part 3)Item 44 · .PDF · 32 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 4 to Part 3)Item 45 · .PDF · 46 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 5 to Part 3)Item 46 · .PDF · 42 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 6 to Part 3)Item 47 · .PDF · 50 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 7 to Part 3)Item 48 · .PDF · 44 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 8 to Part 3)Item 49 · .PDF · 45 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 9 to Part 3)Item 50 · .PDF · 42 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 10 to Part 3)Item 51 · .PDF · 44 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 11 to Part 3)Item 52 · .PDF · 62 KBFuel Control Test Run Report with NX72WP's Fuel Analysis (Part 4)Item 53 · .PDF · 199 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 1 to Part 4)Item 54 · .PDF · 43 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 2 to Part 4)Item 55 · .PDF · 41 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 3 to Part 4)Item 56 · .PDF · 45 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 4 to Part 4)Item 57 · .PDF · 45 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 5 to Part 4)Item 58 · .PDF · 45 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 6 to Part 4)Item 59 · .PDF · 44 KBFuel Control Test Run Report With NX72WP's Fuel Analysis (Attachment 7 to Part 4)Item 60 · .PDF · 32 KB
All 174 files on NTSB’s docket