# Incident 20051119027869I: Beech F33A, Pawhuska, OK, November 19, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 19, 2005, 15:30 local time
- Place: Pawhuska, OK
- Airport: Pawhuska Municipal Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.6717° N, 96.4056° W: Placed by OpenAirDocs at PAWHUSKA MUNI (H76), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.6717&lon=-96.4056&mi=10
- Aircraft: N37050, registered now (https://openairdocs.org/aircraft/N37050) (OpenAirDocs)
- Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH F33A
- Reported engine: CONT IO520*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 960 total, 7 in this make and model, 6 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20051119027869I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON NOVEMBER 19, 2005, A BEECHCRAFT BE-33, PILOTED BY A RATED COMMERCIAL PILOT, RECEIVED MINOR DAMAGE AS A RESULT OF LANDING WITH THE AIRCRAFT'S LANDING GEAR IN THE RETRACTED POSITION AT THE PAWHUSKA MUNICIPAL AIRPORT, PAWHUSKA, OK. THE PILOT WAS NOT INJURED; THERE WERE PASSENGERS ONBOARD. THE PILOT STATED THAT HE DEPARTED BARTLESVILLE, OK EARLIER IN THE AFTERNOON. HE STATED THAT HIS FLIGHT TO PAWHUSKA WAS TO BECOME FAMILIAR WITH A NEW GPS SYSTEM AND TO PRACTICE TAKEOFFS AND LANDINGS. ON THE SECOND APPROACH AND LANDING TO RUNWAY 35, THE PILOT LANDED "GEAR-UP." THE PILOT STATED THAT DURING THE FLARE, HE HEARD A "BUZZER" SOUND AND WAS NOT ALARMED; HE WAS ACCUSTOMED TO HEARING THE STALL WARNING HORN JUST BEFORE TOUCHDOWN DURING SOME OF HIS LANDINGS. HE WENT ON TO STATE THAT HE REALIZED THE LANDING GEAR WAS RETRACTED WHEN THE PROP STRUCK THE GROUND AND THE AIRCRAFT SKIDDED OFF THE RUNWAY. THE PILOT ALSO STATED THAT HE LANDED WITH FLAPS FULL DOWN AND THAT HE WAS ASTONISHED THAT HE NEVER HEARD THE LANDING GEAR WARNING HORN WHILE IN THAT CONFIGURATION. THE PILOT STATED THAT HE DID USE A PRINTED CHECKLIST DURING THE APPROACH AND LANDING SEQUENCE. PILOT ERROR, ACCORDING TO THE PILOT, WAS THE CAUSE OF THIS INCIDENT.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.