20000119041419A

Accident · Substantial damage

FAA accident report · Cessna 208B · Warsaw, IN · January 19, 2000

Date
January 19, 2000 · 22:45 local
Place
Warsaw, IN
Airport
Warsaw Municipal Airport
Phase of flight
Forced/Precautionary Landing
Operating rules
Air taxi and commuter (Part 135)
Operator
DPUA
Damage
Substantial damage
Aircraft
N9457B
NTSB investigation
NTSBCHI00LA059
Reported as
Cessna 208B
Reported engine
Pratt & Whitney PT6A114
People aboard
1
Fatal injuries
0
Pilot’s flight hours
4,500 total1,500 in this make and model60 in the last 90 days

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.

(.19) On January 19, 2000, at 2307 eastern standard time, a Cessna 208B, N9457B, owned and operated by planemasters ltd, of west chicago, Illinois, sustained substantial damage during an on-ground collision with terrain following a precautionary landing and subsequent overrun immediately after takeoff from runway 27 (6,000 feet by 150 feet, snow covered/asphalt) at the Warsaw Municipal Airport, Warsaw, Indiana. Instrument meteorological conditions prevailed at the time of the accident. The cargo flight was operating under the provisions of 14 CFR part 135 and was on an active IFR flight plan. The commercial rated pilot reported no injuries. The flight was originating at the time of the accident and had the intended destination of clark county airport, jeffersonville, Indiana. According to the pilot's written statement, he taxied the airplane to the approach-end of runway 27 and announced on the UNICOM frequency his intentions of taking-off runway 27. The pilot reported that shortly aftet takeoff, "... Noticed a plow truck coming south, and started to abort and realized I couldn't and tried (to) keep flying, but couldn't, and put it (the airplane) down turning to miss any object s...". The aircraft impacted the perimeter fence of the airport and came to rest on a railroad track embankment. The pilot did not report any anomalies with the airplane or its engine. The pilot stated that he did not hear any advisories from the plow truck on the UNICOM frequency. According to the snow-plow operator's written statement, he was removing snow from the taxiway for runway 18/36 which was approximately 100 feet north of runway 09-27 at the time of the accident. The snow-plow operator stated that runway 27 had been cleared of snow eariler in the evening, but had accumulated approximately .25-inches of snow at the time of the accident. (-23) aircraft attempted t/o on rwy 27 at asw. He announced his takeoff on vaicom. Snow plows were clearing snow on taxiway toward end of runway. Pilot saw snowplow, thought it might be on runway and aborted t/o. airport manager indicated that he did not hear a radio call from departing a/c.

As the FAA filed it

(.19) ON JANUARY 19, 2000, AT 2307 EASTERN STANDARD TIME, A CESSNA 208B, N9457B, OWNED AND OPERATED BY PLANEMASTERS LTD, OF WEST CHICAGO, ILLINOIS, SUSTAINED SUBSTANTIAL DAMAGE DURING AN ON-GROUND COLLISION WITH TERRAIN FOLLOWING A PRECAUTIONARY LANDING AND SUBSEQUENT OVERRUN IMMEDIATELY AFTER TAKEOFF FROM RUNWAY 27 (6,000 FEET BY 150 FEET, SNOW COVERED/ASPHALT) AT THE WARSAW MUNICIPAL AIRPORT, WARSAW, INDIANA. INSTRUMENT METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE CARGO FLIGHT WAS OPERATING UNDER THE PROVISIONS OF 14 CFR PART 135 AND WAS ON AN ACTIVE IFR FLIGHT PLAN. THE COMMERCIAL RATED PILOT REPORTED NO INJURIES. THE FLIGHT WAS ORIGINATING AT THE TIME OF THE ACCIDENT AND HAD THE INTENDED DESTINATION OF CLARK COUNTY AIRPORT, JEFFERSONVILLE, INDIANA. ACCORDING TO THE PILOT'S WRITTEN STATEMENT, HE TAXIED THE AIRPLANE TO THE APPROACH-END OF RUNWAY 27 AND ANNOUNCED ON THE UNICOM FREQUENCY HIS INTENTIONS OF TAKING-OFF RUNWAY 27. THE PILOT REPORTED THAT SHORTLY AFTET TAKEOFF, "... NOTICED A PLOW TRUCK COMING SOUTH, AND STARTED TO ABORT AND REALIZED I COULDN'T AND TRIED (TO) KEEP FLYING, BUT COULDN'T, AND PUT IT (THE AIRPLANE) DOWN TURNING TO MISS ANY OBJECT S...". THE AIRCRAFT IMPACTED THE PERIMETER FENCE OF THE AIRPORT AND CAME TO REST ON A RAILROAD TRACK EMBANKMENT. THE PILOT DID NOT REPORT ANY ANOMALIES WITH THE AIRPLANE OR ITS ENGINE. THE PILOT STATED THAT HE DID NOT HEAR ANY ADVISORIES FROM THE PLOW TRUCK ON THE UNICOM FREQUENCY. ACCORDING TO THE SNOW-PLOW OPERATOR'S WRITTEN STATEMENT, HE WAS REMOVING SNOW FROM THE TAXIWAY FOR RUNWAY 18/36 WHICH WAS APPROXIMATELY 100 FEET NORTH OF RUNWAY 09-27 AT THE TIME OF THE ACCIDENT. THE SNOW-PLOW OPERATOR STATED THAT RUNWAY 27 HAD BEEN CLEARED OF SNOW EARILER IN THE EVENING, BUT HAD ACCUMULATED APPROXIMATELY .25-INCHES OF SNOW AT THE TIME OF THE ACCIDENT. (-23) AIRCRAFT ATTEMPTED T/O ON RWY 27 AT ASW. HE ANNOUNCED HIS TAKEOFF ON VAICOM. SNOW PLOWS WERE CLEARING SNOW ON TAXIWAY TOWARD END OF RUNWAY. PILOT SAW SNOWPLOW, THOUGHT IT MIGHT BE ON RUNWAY AND ABORTED T/O. AIRPORT MANAGER INDICATED THAT HE DID NOT HEAR A RADIO CALL FROM DEPARTING A/C.

NTSB investigation

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