# Incident 20130724012479I: Beech A36, Paragould, AR, July 24, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 24, 2013, 18:15 local time
- Place: Paragould, AR
- Airport: Kirk Field
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.0638° N, 90.5092° W: Placed by OpenAirDocs at KIRK FLD (PGR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.0638&lon=-90.5092&mi=10
- Aircraft: N2029P, registered now (https://openairdocs.org/aircraft/N2029P) (OpenAirDocs)
- Registry model: Beech A36 (registry code 1151604, https://openairdocs.org/model/beech-a36) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT MOTOR IO 520 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 8,000 total, 1,500 in this make and model, 20 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130724012479I

## Narrative

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

THE AIRMAN WAS FLYING TRAFFIC PATTERN AT PARAGOULD, AR AIRPORT TO RUNWAY 04. IT WAS THE FIFTH FLIGHT IN PAST TWO HOURS. ADJUSTMENTS TO THE FUEL CONTROL HAD BEEN MADE AND THE FLIGHT WAS TO VERIFY FUEL FLOW INDICATIONS. THE FUEL FLOW ADJUSTMENT WAS SATISFACTORY AND THERE WAS NO MECHANICAL RELATED CAUSE IN THIS INCIDENT.

WHILE FLYING THE TRAFFIC PATTERN, THE AIRMAN STATED HE WAS MONITORING THE FUEL CONTROL GAUGE. THE INDICATIONS WERE ALL NORMAL SO HE WAS USING THE PATTERN AS PRACTICE OF THE ARRIVAL PROFILE FOR AN UPCOMING TRIP TO OSHKOSH WHICH REQUIRED A SLOWER SPEED AND HIGHER TRAFFIC PATTERN ALTITUDE FROM STANDARD PATTERN. THE PASSENGER, ALSO A RATED AIRMAN, WAS CONVERSING THROUGHOUT THE FLIGHT ABOUT HIS PREVIOUS OSHKOSH FLIGHT EXPERIENCE.

THE AIRMAN WAS DISTRACTED BY A COMBINATION OF THREE THINGS: MONITORING THE FUEL FLOW INDICATOR

THE PASSENGER IN THE AIRCRAFT

FLYING A NON-STANDARD PATTERN

THESE THREE THINGS IN COMBINATION, RESULTED IN THE AIRMAN NOT VERIFYING THE GEAR WAS DOWN PRIOR TO LANDING AND FAILURE TO EXTEND THE GEAR PRIOR TO LANDING.

AIRMAN STATED HE DID NOT HEAR THE GEAR HORN AND WAS NOT SURE IF IT DID SOUND OFF DUE TO THE ADDITIONAL POWER HE WAS CARRYING PRIOR TO LANDING.

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.