OpenAirDocs.org

19990919033709A

Accident · Destroyed
Open the Markdown

FAA accident report · Scwzer G-164B · Enterprise, AL · September 19, 1999

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
September 19, 1999 · 09:20 local
Place
Enterprise, AL
Phase of flight
Final Approach
Operating rules
Agricultural (Part 137)
Damage
Destroyed
Aircraft
N6736Q
NTSB investigation
NTSBATL99LA133
Reported as
Scwzer G164B
Reported engine
Garrett TPE33143A
Fatal injuries
0
Pilot’s flight hours
10,860 total2,340 in this make and model
N6736QRegistration cancelled Aug 5, 2013 · Grumman Acft ENG Cor-Schweizer G-164BS/N 250B · Built 1977Airframe modelGrumman Acft ENG Cor-Schweizer G-164BEngine modelPratt & Whitney R-985 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) The pilot-in-command (PIC) reported the aircraft engine surged just after his 0900L takeoff from Enterprise airport, AL (edn) on September 19, 1999. The sound of the engine surge was witnessed by several bystanders. He attempted a return to edn for an emergency landing but reported an inbound Cessna 150 flew under his path causing him to abort. The engine failed during his second attempt to land. He managed to set the aircraft down at 0925L in an un-tilled field approx. 3/4 of a mile off the approach end of runway 05. The PIC was able to exit the wreckage just before it engulging into flames. A witness arrived moments later to asist hime and subsequently took him to the airport to wash chemicals out of this eyes. He was later transported to a local hospital and treated for minor injuries before being released. There was no radio contact between the Cessna 150 and the accident aircraft (6736Q). The accident aircraft was not equipped with a radio, according to the PIC. "See attached" (.4) according to the pilot, he departed Enterprise airport with a full load of chemicals for aerial application to a nearby cotton field. Shortly after takeoff, the engine began to surge . He adjusted the propeller lever control to the 'high' position and turned the fuel boost pump 'on.' He elected to return to the airport and while on short final he observed another airplane pass beneath him. His airplane, although surging, had been producing sufficient power therefore, he executed a left 360 degree turn for spacing. When the turn was nearly complete, the engine lost all power and he maneuvered for an open field. The airplane collided with a tree and then the ground. Examination of the wreckage revealed that the wings, empennage, and fuselage were destroyed almost beyond recognition. The only recognizable portion of the engine was the power section and the entire turbine section was destroyed. A fuel sample of the jet-a fuel used in the airplane showed no visible evidence of contamination. The airplane and engine were consumed by fire.

As the FAA filed it

(-23) THE PILOT-IN-COMMAND (PIC) REPORTED THE AIRCRAFT ENGINE SURGED JUST AFTER HIS 0900L TAKEOFF FROM ENTERPRISE AIRPORT, AL (EDN) ON SEPTEMBER 19, 1999. THE SOUND OF THE ENGINE SURGE WAS WITNESSED BY SEVERAL BYSTANDERS. HE ATTEMPTED A RETURN TO EDN FOR AN EMERGENCY LANDING BUT REPORTED AN INBOUND CESSNA 150 FLEW UNDER HIS PATH CAUSING HIM TO ABORT. THE ENGINE FAILED DURING HIS SECOND ATTEMPT TO LAND. HE MANAGED TO SET THE AIRCRAFT DOWN AT 0925L IN AN UN-TILLED FIELD APPROX. 3/4 OF A MILE OFF THE APPROACH END OF RUNWAY 05. THE PIC WAS ABLE TO EXIT THE WRECKAGE JUST BEFORE IT ENGULGING INTO FLAMES. A WITNESS ARRIVED MOMENTS LATER TO ASIST HIME AND SUBSEQUENTLY TOOK HIM TO THE AIRPORT TO WASH CHEMICALS OUT OF THIS EYES. HE WAS LATER TRANSPORTED TO A LOCAL HOSPITAL AND TREATED FOR MINOR INJURIES BEFORE BEING RELEASED. THERE WAS NO RADIO CONTACT BETWEEN THE CESSNA 150 AND THE ACCIDENT AIRCRAFT (6736Q). THE ACCIDENT AIRCRAFT WAS NOT EQUIPPED WITH A RADIO, ACCORDING TO THE PIC. "SEE ATTACHED" (.4) ACCORDING TO THE PILOT, HE DEPARTED ENTERPRISE AIRPORT WITH A FULL LOAD OF CHEMICALS FOR AERIAL APPLICATION TO A NEARBY COTTON FIELD. SHORTLY AFTER TAKEOFF, THE ENGINE BEGAN TO SURGE . HE ADJUSTED THE PROPELLER LEVER CONTROL TO THE 'HIGH' POSITION AND TURNED THE FUEL BOOST PUMP 'ON.' HE ELECTED TO RETURN TO THE AIRPORT AND WHILE ON SHORT FINAL HE OBSERVED ANOTHER AIRPLANE PASS BENEATH HIM. HIS AIRPLANE, ALTHOUGH SURGING, HAD BEEN PRODUCING SUFFICIENT POWER THEREFORE, HE EXECUTED A LEFT 360 DEGREE TURN FOR SPACING. WHEN THE TURN WAS NEARLY COMPLETE, THE ENGINE LOST ALL POWER AND HE MANEUVERED FOR AN OPEN FIELD. THE AIRPLANE COLLIDED WITH A TREE AND THEN THE GROUND. EXAMINATION OF THE WRECKAGE REVEALED THAT THE WINGS, EMPENNAGE, AND FUSELAGE WERE DESTROYED ALMOST BEYOND RECOGNITION. THE ONLY RECOGNIZABLE PORTION OF THE ENGINE WAS THE POWER SECTION AND THE ENTIRE TURBINE SECTION WAS DESTROYED. A FUEL SAMPLE OF THE JET-A FUEL USED IN THE AIRPLANE SHOWED NO VISIBLE EVIDENCE OF CONTAMINATION. THE AIRPLANE AND ENGINE WERE CONSUMED BY FIRE.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB ATL99LA133Accident · Minor injuriesLimited investigationFinal reportEnterprise, ALThe loss of engine power for undetermined reasons. Contributing to the severity of the accident was the in-flight collision with a tree during the forced landing.Sep 19, 1999 · Destroyed

Other reports on N6736Q · 1

Matched to the same aircraft by N-number and date.

Accident 19840116001779AFcd/Prec Ldg From Cruise · Homestead, FLCollided with the ground after engine failure. NR8 cylinder failed from fatigue cracking near the valve end.Jan 16, 1984 · Destroyed