# Accident 20000712007379A: Cessna 337G, Battle Mountain, NV, July 12, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 12, 2000, 18:45 local time
- Place: Battle Mountain, NV
- Airport: Lander County Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 40.4700° N, 117.0302° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.4700&lon=-117.0302&mi=10
- Aircraft: N3273D, registered now (https://openairdocs.org/aircraft/N3273D) (OpenAirDocs)
- Registry model: Cessna 337G (registry code 2075730, https://openairdocs.org/model/cessna-337g) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 337G
- Reported engine: CONT IO360G
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,600 total, 69 in this make and model, 432 in the last 90 days
- NTSB investigation: [NTSB LAX00TA263](https://openairdocs.org/ntsb/LAX00TA263) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000712007379A

## Narrative

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

(-23) ON LANDING AT BATTLE MOUNTAIN, NNV. (BAM) PILOT P.C. DAVIS STATED THAT HE DID NOT USE A CHECKLIST AND HE FORGOT TO PUT THE LANDING GEAR DOWN. (.4) ON JULY 12, 2000, AT 1845 HOURS PACIFIC DAYLIGHT TIME, A CESSNA 337G, N3273D, LANDED GEAR UP AT THE BATTLE MOUNTAIN, NEVADA, AIRPORT. THE AIRPLANE WAS OPERATED BY THE U.S. DEPARTMENT OF INTERIOR, BUREAU OF LAND MANAGEMENT AS A PUBLIC-USE FLIGHT, UNDER 14 CFR PART 91, AND SUSTAINED SUBSTANTIAL DAMAGE. THE COMMERCIAL PILOT AND ONE PASSENGER WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS EXISTED FOR THE CROSS-COUNTRY FLIGHT THAT DEPARTED THE BOISE, IDAHO AIRPORT AT 1730, AND WAS SCHEDULED TO TERMINATE AT BATTLE MOUNTAIN. A VISUAL FLIGHT RULES (VFR) FLIGHT PLAN HAD BEEN FILED. IN AN INTERVIEW WITH A FEDERAL AVIATION ADMINISTRATION INSPECTOR, THE PILOT STATED THAT HE FORGOT TO PUT THE LANDING GEAR DOWN. HE INDICATED THAT BECAUSE HE HAD KEPT HIS AIRSPEED UP DURING THE DESCENT FOR A HIGH ALTITUDE LANDING, THE LANDING GEAR WARNING HORN DID NOT ACTIVATE. HE HAD FLOWN THE AIRPLANE EARLIER THAT DAY FROM BATTLE MOUNTAIN TO BOISE TO EXCHANGE FIREFIGHTING CREWS, AND NO DISCREPANCIES WERE NOTED WITH THE LANDING GEAR SYSTEM. IN AN INTERVIEW   WITH AN AIR SAFETY INVESTIGATOR FROM THE U.S. DEPARTMENT OF THE INTERIOR, OFFICE OF AIRCRAFT SERVICES, THE PILOT STATED THAT DURING THE LANDING FLARE HE DID NOT HEAR THE LANDING GEAR WARNING HORN SOUND. HE REPORTED THAT HE DID NOT CHECK THAT THE LANDING GEAR GREEN LIGHT WAS ILLUMINATED, OR VISUALLY VERIFY WITH THE MIRROR LOCATED ON THE OUTSIDE OF THE AIRPLANE TO SEE IF THE LANDING GEAR WAS EXTENDED. HE FURTHER STATED THAT HE DID NOT VERIFY THAT THE LANDING GEAR HANDLE WAS IN THE DOWN POSITION. THE PILOT INDICATED THAT HE DID NOT FOLLOW A MENTAL OR PRINTED CHECKLIST FOR LANDING, AND THAT THERE WAS NOT A PRINTED CHECKLIST FOR PUTTING THE LANDING GEAR DOWN.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX00TA263](https://openairdocs.org/ntsb/LAX00TA263), Jul 13, 2000: Cessna 337G (N3273D), Battle Mountain, NV, substantial damage. Probable cause: Failure of the pilot to extend the landing gear, and his failure to follow the published before landing checklist concerning extension of the landing gear.

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.