20031201032609I

Incident · Minor damage

FAA incident report · Beech F33A · Minden, NV · December 1, 2003

Date
December 1, 2003
Place
Minden, NV
Airport
Douglas County Airport
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N961WW
Reported as
Beech F33A
People aboard
1
Fatal injuries
0
Pilot’s flight hours
1,718 total1,103 in this make and model45 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.

(-23) Pilot statement: on dec. 1, 2003, my aircraft, a Beech bonanza F33A (N961WW) was scheduled to go in for an annual inspection. I had made an appointment for the annual about three weeks earlier with privacy data omitted of air sierra, inc. at Minden airport (mev). I checked with air sierra early on dec. 1 to make sure they were ready to take my plane. They recommended that I bring the plane in with the engine warmed up so they could do an immediate compression check and start the draining for an oil change. I proceeded to my hangar to get my plane and decided to fly one time around the local traffic pattern at Minden to do the warm up. Before taking the plane out of the hangar, I did a complete preflight inspection iaw the POH. No defects or unusual conditions were noted. After engine start I listened to wx on AWOS 119.325. Wind was calm no adverse cloud or other wx conditions were reported. I set the altimeter to the reported value. Upon starting to taxi, I heard another aircraft in the traffic pattern, and I recognized it to be a Piper cherokee which belongs to the flying start aero flight school at Minden. I called UNICOM on 122.80 and asked for a radio check. I received no reply from the ground but the instructor in the Piper said he heared me loud and clear. I proceeded then to taxi out to the runup pad and also announced on 122.80 that I was taxiing from south hangars to runway 34. Upon reaching the run up pad area at runway 34, I proceeded to do the flight control and engine run up in accordance with the POH checklist. Everything checked normal including the voltage and amperage, instrument air, prop, and engine magnetos and gauges. After completing the before takeoff checklist, I circled the aircraft to visually inspect the traffic pattern and I saw the other aircraft from the flight school on final. I held my position and waited until that aircraft had done a touch and go and was turning crosswind to downwind in the pattern before starting my takeoff. I announced on 122.80 that I was taking runway 34 at Minden for left closed traffic. Upon taking the runway and giving the engine full throttle, I leaned the mixture for field elevation/fuel flow and proceeded with the takeoff. Everything operated normally on takeoff, and I retracted the gear on climb out to pattern altitude. I self announced my crosswind leg and also again on turning to downwind. When established on downwind, I was at pattern altitude, and I remember reaching and lowering the gear handle because it is my practice to always lower the gear before lowering the flaps. I remember then lowering flaps to 10 degrees. (My usual downwind configuration is 15 inches manifold, gear down, 10 degrees flaps. This gives me 100 mph indicated airspeed and establishes the rest of the pattern procedure). I self announced my downwind leg position (midfield) on 122.80. It was at this point that I heard a corporate jet (I believe it was a Cessna citation, but I can't remember the call sign) announce a four mile straight-in final to runway 34 at Minden. Also within a matter of two or three seconds, the Piper ahead of me announced his turn to the base leg. I immediately diverted by attention to see if I could pick up a visual on the incoming jet because I had not heard an acknowledgment from either the Piper or the jet as to a possible conflict. (This has happened several times at Minden where corporate and other large aircraft make straight in approaches when others are in a left traffic pattern and are self announcing their positions). My intent was to alert the Piper in case he hadmissed the call from the incoming jet. It was in this short time of about 5-10 seconds that my attention was diverted from completing the required "gumps" check. I do remember specifically checking the mixture and the prop controls. The aircraft felt normal for the airspeeds and throttle settings that I used and I heard no unusual sounds. After seeing that the jet had landed and the Piper was number 2 behind them, I extended my downwind about a quarter of a mile to allow for some additional spacing. I proceeded to turn to base leg, lowered flaps to 20 degrees, and self announced. At this point I saw that the jet had cleared the runway and the Piper was over the numbers to do a touch and go. I then turned and self announced a one half mile final to runway 34 and a full stop. I lowered the last notch of flaps to full, and flew the rest of the approach to the runway surface. The first indication of a problem was in the flare just above the runway surface and I observed the prop coming to a stop, tips bent, and the aircraft settling onto the surface in a slide. There was absolutely no sound from the gear up warning horn. The aircraft came to a stop after sliding approximately 200 yardsand I noticed a distinct odor like that of burning electrical circuits. My immediate reaction was to shut down the master switch and exit the aircraft as soon as possible because the fuel tanks were full. On the way out of the aircraft, I did pick up the microphone and announced that I had landed gear up and was blocking the runway. The instructor in the Piper then relayed the message and airport personnel arrived to the scene shortly thereafter. The airport manager, privacy data omitted, took digital photos of the aircraft exterior and inside the cockpit. (These photos are available at the airport office). Several maintenance personnel came out to the scene and after securing permission from the FAA, the aircraft was lifted by a forklift and chain and the gear was manually cranked down. The aircraft was then towed back to hangar E-9 where it awaits inspection by the FAA and insurance company personnel. Additional notes: tach ttsn = 2568.4 current engine is a factory reman installed at tach 1367.8.

As the FAA filed it

(-23) PILOT STATEMENT: ON DEC. 1, 2003, MY AIRCRAFT, A BEECH BONANZA F33A (N961WW) WAS SCHEDULED TO GO IN FOR AN ANNUAL INSPECTION. I HAD MADE AN APPOINTMENT FOR THE ANNUAL ABOUT THREE WEEKS EARLIER WITH ^PRIVACY DATA OM^ OF AIR SIERRA, INC. AT MINDEN AIRPORT (MEV). I CHECKED WITH AIR SIERRA EARLY ON DEC. 1 TO MAKE SURE THEY WERE READY TO TAKE MY PLANE. THEY RECOMMENDED THAT I BRING THE PLANE IN WITH THE ENGINE WARMED UP SO THEY COULD DO AN IMMEDIATE COMPRESSION CHECK AND START THE DRAINING FOR AN OIL CHANGE. I PROCEEDED TO MY HANGAR TO GET MY PLANE AND DECIDED TO FLY ONE TIME AROUND THE LOCAL TRAFFIC PATTERN AT MINDEN TO DO THE WARM UP. BEFORE TAKING THE PLANE OUT OF THE HANGAR, I DID A COMPLETE PREFLIGHT INSPECTION IAW THE POH. NO DEFECTS OR UNUSUAL CONDITIONS WERE NOTED. AFTER ENGINE START I LISTENED TO WX ON AWOS 119.325. WIND WAS CALM NO ADVERSE CLOUD OR OTHER WX CONDITIONS WERE REPORTED. I SET THE ALTIMETER TO THE REPORTED VALUE. UPON STARTING TO TAXI, I HEARD ANOTHER AIRCRAFT IN THE TRAFFIC PATTERN, AND I RECOGNIZED IT TO BE A PIPER CHEROKEE WHICH BELONGS TO THE FLYING START AERO FLIGHT SCHOOL AT MINDEN. I CALLED UNICOM ON 122.80 AND ASKED FOR A RADIO CHECK. I RECEIVED NO REPLY FROM THE GROUND BUT THE INSTRUCTOR IN THE PIPER SAID HE HEARED ME LOUD AND CLEAR. I PROCEEDED THEN TO TAXI OUT TO THE RUNUP PAD AND ALSO ANNOUNCED ON 122.80 THAT I WAS TAXIING FROM SOUTH HANGARS TO RUNWAY 34. UPON REACHING THE RUN UP PAD AREA AT RUNWAY 34, I PROCEEDED TO DO THE FLIGHT CONTROL AND ENGINE RUN UP IN ACCORDANCE WITH THE POH CHECKLIST. EVERYTHING CHECKED NORMAL INCLUDING THE VOLTAGE AND AMPERAGE, INSTRUMENT AIR, PROP, AND ENGINE MAGNETOS AND GAUGES. AFTER COMPLETING THE BEFORE TAKEOFF CHECKLIST, I CIRCLED THE AIRCRAFT TO VISUALLY INSPECT THE TRAFFIC PATTERN AND I SAW THE OTHER AIRCRAFT FROM THE FLIGHT SCHOOL ON FINAL. I HELD MY POSITION AND WAITED UNTIL THAT AIRCRAFT HAD DONE A TOUCH AND GO AND WAS TURNING CROSSWIND TO DOWNWIND IN THE PATTERN BEFORE STARTING MY TAKEOFF. I ANNOUNCED ON 122.80 THAT I WAS TAKING RUNWAY 34 AT MINDEN FOR LEFT CLOSED TRAFFIC. UPON TAKING THE RUNWAY AND GIVING THE ENGINE FULL THROTTLE, I LEANED THE MIXTURE FOR FIELD ELEVATION/FUEL FLOW AND PROCEEDED WITH THE TAKEOFF. EVERYTHING OPERATED NORMALLY ON TAKEOFF, AND I RETRACTED THE GEAR ON CLIMB OUT TO PATTERN ALTITUDE. I SELF ANNOUNCED MY CROSSWIND LEG AND ALSO AGAIN ON TURNING TO DOWNWIND. WHEN ESTABLISHED ON DOWNWIND, I WAS AT PATTERN ALTITUDE, AND I REMEMBER REACHING AND LOWERING THE GEAR HANDLE BECAUSE IT IS MY PRACTICE TO ALWAYS LOWER THE GEAR BEFORE LOWERING THE FLAPS. I REMEMBER THEN LOWERING FLAPS TO 10 DEGREES. (MY USUAL DOWNWIND CONFIGURATION IS 15 INCHES MANIFOLD, GEAR DOWN, 10 DEGREES FLAPS. THIS GIVES ME 100 MPH INDICATED AIRSPEED AND ESTABLISHES THE REST OF THE PATTERN PROCEDURE). I SELF ANNOUNCED MY DOWNWIND LEG POSITION (MIDFIELD) ON 122.80. IT WAS AT THIS POINT THAT I HEARD A CORPORATE JET (I BELIEVE IT WAS A CESSNA CITATION, BUT I CAN'T REMEMBER THE CALL SIGN) ANNOUNCE A FOUR MILE STRAIGHT-IN FINAL TO RUNWAY 34 AT MINDEN. ALSO WITHIN A MATTER OF TWO OR THREE SECONDS, THE PIPER AHEAD OF ME ANNOUNCED HIS TURN TO THE BASE LEG. I IMMEDIATELY DIVERTED BY ATTENTION TO SEE IF I COULD PICK UP A VISUAL ON THE INCOMING JET BECAUSE I HAD NOT HEARD AN ACKNOWLEDGMENT FROM EITHER THE PIPER OR THE JET AS TO A POSSIBLE CONFLICT. (THIS HAS HAPPENED SEVERAL TIMES AT MINDEN WHERE CORPORATE AND OTHER LARGE AIRCRAFT MAKE STRAIGHT IN APPROACHES WHEN OTHERS ARE IN A LEFT TRAFFIC PATTERN AND ARE SELF ANNOUNCING THEIR POSITIONS). MY INTENT WAS TO ALERT THE PIPER IN CASE HE HADMISSED THE CALL FROM THE INCOMING JET. IT WAS IN THIS SHORT TIME OF ABOUT 5-10 SECONDS THAT MY ATTENTION WAS DIVERTED FROM COMPLETING THE REQUIRED "GUMPS" CHECK. I DO REMEMBER SPECIFICALLY CHECKING THE MIXTURE AND THE PROP CONTROLS. THE AIRCRAFT FELT NORMAL FOR THE AIRSPEEDS AND THROTTLE SETTINGS THAT I USED AND I HEARD NO UNUSUAL SOUNDS. AFTER SEEING THAT THE JET HAD LANDED AND THE PIPER WAS NUMBER 2 BEHIND THEM, I EXTENDED MY DOWNWIND ABOUT A QUARTER OF A MILE TO ALLOW FOR SOME ADDITIONAL SPACING. I PROCEEDED TO TURN TO BASE LEG, LOWERED FLAPS TO 20 DEGREES, AND SELF ANNOUNCED. AT THIS POINT I SAW THAT THE JET HAD CLEARED THE RUNWAY AND THE PIPER WAS OVER THE NUMBERS TO DO A TOUCH AND GO. I THEN TURNED AND SELF ANNOUNCED A ONE HALF MILE FINAL TO RUNWAY 34 AND A FULL STOP. I LOWERED THE LAST NOTCH OF FLAPS TO FULL, AND FLEW THE REST OF THE APPROACH TO THE RUNWAY SURFACE. THE FIRST INDICATION OF A PROBLEM WAS IN THE FLARE JUST ABOVE THE RUNWAY SURFACE AND I OBSERVED THE PROP COMING TO A STOP, TIPS BENT, AND THE AIRCRAFT SETTLING ONTO THE SURFACE IN A SLIDE. THERE WAS ABSOLUTELY NO SOUND FROM THE GEAR UP WARNING HORN. THE AIRCRAFT CAME TO A STOP AFTER SLIDING APPROXIMATELY 200 YARDSAND I NOTICED A DISTINCT ODOR LIKE THAT OF BURNING ELECTRICAL CIRCUITS. MY IMMEDIATE REACTION WAS TO SHUT DOWN THE MASTER SWITCH AND EXIT THE AIRCRAFT AS SOON AS POSSIBLE BECAUSE THE FUEL TANKS WERE FULL. ON THE WAY OUT OF THE AIRCRAFT, I DID PICK UP THE MICROPHONE AND ANNOUNCED THAT I HAD LANDED GEAR UP AND WAS BLOCKING THE RUNWAY. THE INSTRUCTOR IN THE PIPER THEN RELAYED THE MESSAGE AND AIRPORT PERSONNEL ARRIVED TO THE SCENE SHORTLY THEREAFTER. THE AIRPORT MANAGER, ^PRIVACY DATA OMI^, TOOK DIGITAL PHOTOS OF THE AIRCRAFT EXTERIOR AND INSIDE THE COCKPIT. (THESE PHOTOS ARE AVAILABLE AT THE AIRPORT OFFICE). SEVERAL MAINTENANCE PERSONNEL CAME OUT TO THE SCENE AND AFTER SECURING PERMISSION FROM THE FAA, THE AIRCRAFT WAS LIFTED BY A FORKLIFT AND CHAIN AND THE GEAR WAS MANUALLY CRANKED DOWN. THE AIRCRAFT WAS THEN TOWED BACK TO HANGAR E-9 WHERE IT AWAITS INSPECTION BY THE FAA AND INSURANCE COMPANY PERSONNEL. ADDITIONAL NOTES: TACH TTSN = 2568.4 CURRENT ENGINE IS A FACTORY REMAN INSTALLED AT TACH 1367.8.

Other reports on N961WW · 1

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