IAD01LA068

The airplane was in cruise flight at 6,500 feet, about 7 miles west of the airport, when the engine lost partial power. The pilot contacted Danbury tower, proceeded direct to the airport, and circled about 1 mile west of the runway to lose altitude. The controller provided weather information and asked the pilot if he would like to land on runway 26 or 35. The pilot opted for runway 26 because it was longer. Upon passing through 3,000 feet, the controller asked the pilot if he could make a left 270 degree turn, and the pilot acknowledged. About a minute later, the pilot reported that the engine was running rough, but still producing power. While on final approach, the pilot made s-turns, and the controller gave him the option to make another 270 degree turn to lose altitude. On final approach, witnesses observed the airplane in a "dramatic" slip, and that it was too high and fast to land on the 4,422 foot long runway. At mid-field, the airplane was still "extremely fast" at a height level with the control tower, about 62 feet. Near the end of the runway, the pilot applied power to go-around, but the engine did not respond. The airplane continued to descend and collided with a pole about a 1/4- mile from the end of runway 8. Examination of the engine revealed that the #3 exhaust stack exhibited a 3/4-inch wide horizontal crack along the rim of the weld line. Additionally, the pilot had a 3,135 foot long perpendicular runway available for landing.

History of flight

On June 9, 2001, at 0847 eastern daylight time, a Grumman American AA-5A, N27221, was substantially damaged during a go-around to runway 26 at Danbury Municipal Airport (DXR), Danbury, Connecticut. The certificated private pilot and pilot rated passenger sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 CFR Part 91.

The pilot and passenger departed Hartford, Connecticut, about 0820, destined for Reading, Pennsylvania. The airplane was level at 6,500 feet about 7 miles west of Danbury when the pilot felt a shimmy in the control yoke, and noticed a drop in engine rpm and exhaust gas temperature. The pilot set the engine power to 1,800 rpm, contacted Danbury tower, and requested that emergency equipment be standing by.

Danbury tower then informed the pilot that the winds were from 360 degrees at 7 knots, and that runways 35 and 26 were active.

The pilot elected to land on runway 26 because it was longer.

In a written statement, the pilot said:

"We proceeded to circle and descend about a mile East of the numbers of RY26. As we were making a turn perpendicular to the numbers of RY26, Tower told us to make a 270 degree turn to follow a Cessna on close-in left base. I was surprised by this instruction, since we thought we declared an emergency, but we still needed to lose a little more altitude, so we complied. We never thought that the Cessna would be a factor for us.

"Twice during the descent, we added power to see if the engine was still producing any power. Both times the RPM's did climb, so we thought we had partial power.

"As we turned final, the Controller asked if we could make another 270 degree turn to follow the Cessna, who had slowed down on final. The request for a 270 degree turn was confusing, since we were now on final, not base. I believe that we told the Controller unable, but did s-turns instead. The controller told the Cessna on final to keep it's speed up at least once, maybe twice.

"When we originally turned final, we still appeared to be a little high, but I didn't think we were high enough to make a 360 degree turn back around to final. That's when the Controller asked us to make second 270 degree turn. My plan was to make two s-turns, and then perform a slip, adding flaps as necessary. I made two s-turns, but unfortunately they were ineffective. I was still a little high, and actually picked up a little airspeed. As I came out of the second s-turn, I started to slip, and my partner added some flaps. Our projectory for landing was about halfway down RY26. I felt things were in control, and that we would make a safe landing. That's when I looked up and saw that the Cessna was still on the runway, at the point we were aiming to land. It appeared the Cessna had stopped on the runway!

"At that moment, we thought it was too dangerous to try and land with the Cessna still on the runway. I leveled out , and attempted to go around. I thought the partial power that we believed we had, was enough to circle around again and land RY26. When we added power, however, we got no response from the engine. We were a glider at that point! My partner retracted the partial flaps. I lowered the nose and looked for a spot to land. We didn't have enough altitude to circle to another runway. There were trees straight ahead, so we turned approximately 15 degrees to the right, and headed for a small portion of a road that we could see. We impacted the ground, and the plane started turning to the left.

"I believe the Cessna and the actions of the Controller was a major distraction. Trying to land an aircraft with no power is trying enough, but having to deal with another aircraft in the picture was more than I needed at that time."

Three witnesses were interviewed by two Safety Board air traffic control (ATC) specialists. According to the ATC specialists' factual report, the first witness, a flight instructor, was in the right seat of a Cessna 172 at the departure end of runway 26. The nose of the airplane was pointed southeast, and a student was seated in the left seat.

The witness observed the Grumman performing s-turns, and stated that the airplane appeared to be "too high" and "fast" to land.

As the Grumman crossed over the displaced threshold for runway 26, the witness told his student that the airplane was not going to land because it was "too high." He also observed the Grumman in a "very dramatic left slip" about 100-150 feet above the runway as it passed over intersection C2. The witness then saw the Grumman level out and collide with trees located beyond airport property.

A second witness, who was also a flight instructor, was seated in a low wing Piper airplane at the hold-short line for runway 26. The airplane was facing east, which was perpendicular to the runway.

The witness heard the pilot of the Grumman broadcast "something about a rough engine." He then observed a Cessna on final approach with the Grumman following behind it, but explained that they were not too close together.

The witness heard the Grumman pilot request s-turns, after which he observed the airplane executing "tight" s-turns. He then observed the Grumman turn to a 270 degree heading, and stated that the pilot "really racked it around." The witness estimated that the Grumman had exceeded 45 degree bank angles and was concerned that it would stall and spin.

The witness also reported that the Grumman was "really high and really fast" on approach, and that there was no way that it could have landed at the airport based on it's height and rapid speed.

A third witness was seated in a low wing Piper airplane at the east end of runway 26. He had just taxied to the ramp, when he heard the tower controller communicating with the pilot of the Grumman. He also heard the controller state that there was a Cessna in the pattern. At that time, the witness turned his attention to runway 26, because he was the owner of the Cessna and the pilot was his employee.

The witness observed the Grumman flying "high and fast", and catching up to the Cessna. He said that when the Cessna was on a "normal" climb out, the Grumman had just crossed the runway 26 threshold. He believed that the Grumman was going to land around intersection "A", which was located at the departure end of runway 26.

Personnel information

The pilot held a private pilot certificate with a rating for airplane single-engine land. His most recent Federal Aviation Administration (FAA) second class medical certificate was issued on January 17, 2001. The pilot was also a certificated FAA control tower operator at Bradley International Airport (BDL), Windsor Locks, Connecticut .

The pilot reported a total of 455 flight hours, of which 270 hours were in make and model.

Airport information

Danbury Municipal Airport was a controlled airport with two intersecting runways; runway 8/26 and runway 17/35. There were trees obstructing the approach paths to runways 8, 26, and 35, and a pole obstructing the approach path to runway 17. Runway 26 was 4,422 feet long and 150 feet wide with a displaced threshold 734 feet from the approach end of the runway. Runway 35 was 3,135 feet long and 100 feet wide with a displaced threshold 231 feet from the approach end of the runway.

The air traffic control tower was located to the west of runway 17/35 and to the north of runway 08/26. The height of the control tower was 62 feet agl.

Wreckage and impact information

An FAA inspector performed an on scene examination of the airplane. According to the inspector, the airplane crossed a road, collided with a light pole about 1/4-mile from the approach end of runway 8. The airplane also missed colliding with a FedEx building by several feet. The airplane separated into three sections and came to rest on residenti