# Accident 20010727020249A: Tcraft BC12D, Wall, SD, July 27, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 27, 2001, 18:00 local time
- Place: Wall, SD
- Airport: Wall Municipal Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 43.9908° N, 102.2303° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=43.9908&lon=-102.2303&mi=10
- Aircraft: N39971, a cancelled registration (https://openairdocs.org/deregistered/N39971-2007-09-20) (OpenAirDocs)
- Registry model: Taylorcraft BC12-D (registry code 8850316, https://openairdocs.org/model/taylorcraft-bc12-d) (OpenAirDocs)
- Registry engine: Continental A&C65 series (registry code 17003, https://openairdocs.org/engine/continental-a-c65-series) (OpenAirDocs)
- Reported make and model: TCRAFT BC12D
- Pilot certificates: Student
- NTSB investigation: [NTSB CHI01LA254](https://openairdocs.org/ntsb/CHI01LA254) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010727020249A

## Narrative

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

(.19) ON JULY 27, 2001, AT 1800 CENTRAL DAYLIGHT TIME, A TAYLORCRAFT BC12-D, N39971, SUSTAINED SUBSTANTIAL DAMAGE DURING LANDING ROLL WHEN IT NOSED OVER IN A FIELD. THE 14 CFR PART 91 BUSINESS FLIGHT HAD DEPARTED FROM A PRIVATE AIRSTRIP EN ROUTE TO THE WALL MUNICIPAL AIRPORT (6V4), WALL, SOUTH DAKOTA. THE PILOT REPORTED THE ENGINE WAS RUNNING ROUGH DURING A GO-AROUND TO THE RUNWAY.  THE PILOT LANDED ABOUT 150 YARDS PAST THE RUNWAY ON THE SECOND LANDING ATTEMPT AND THE AIRPLANE NOSED OVER.  THE PILOT WAS NOT INJURED.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED.    (-23) ON JULY 27, 2001 AT 1700 MOUNTAIN DAYLIGHT TIME, A TAYLORCRAFT BC12-D (TAILWHEEL AIRCRAFT), N39971, OWNED AND OPERATED BY JAMES NACHTIGALL, SUSTAINED SUBSTANTIAL DAMAGE DURING AN ATTEMPTED "GO-AROUND" AT THE WALL MUNICIPAL AIRPORT (6V4), WALL, SD. THE STUDENT PILOT STATED: "I APPROACHED THE RUNWAY AT 65 MPH AND WAS ATTEMPTING TO MAKE A WHEEL LANDING. THE AIRCRAFT CONTINUED TO FLOAT DOWN THE RUNWAY. SHORTLY AFTER THE MAIN GEAR TOUCHED DOWN, I DECIDED TO DO A GO-AROUND BECAUSE I WAS RUNNING OUT OF RUNWAY. I ADDED FULL POWER. THE ENGINE SOUNDED OK AND WAS RUNNING SMOOTH, HOWEVER THE AIRCRAF T DID NOT SEEM LIKE IT HAD ENOUGH POWER TO CLIMB OUT LIKE IT USUALLY DOES. I PULLED BACK ON THE ELEVATOR AND CLIMBED A FEW FEET TO AVOID SOME RUNWAY LIGHTS, THE LEFT WING DIPPED AND THE AIRCRAFT CONTROLS DID NOT SEEM TO BE VERY EFFECTIVE." THE AIRCRAFT IMPACTED IN A FIELD OFF THE RUNWAY AND THE AIRCRAFT NOSED OVER CAUSING SUBSTANTIAL DAMAGE TO THE AIRCRAFT. THE STUDENT PILOT DID NOT RECEIVE ANY INJURIES. INVESTIGATION OF THE AIRCRAFT AND A FOLLOW-UP INTERVIEW WITH THE PILOT REVEALED NO MALFUNCTION OF THE POWERPLANT.

## 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 CHI01LA254](https://openairdocs.org/ntsb/CHI01LA254), Jul 27, 2001: Taylorcraft BC12-D (N39971), Wall, SD, substantial damage. Probable cause: The student pilot failed to maintain a proper glidepath, failed to obtain proper climb rate, and executed the go-around improperly. Additional factors included the pilot's lack of experience, the…

## Other reports on N39971 (1)

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

- [Accident 20041106029999A](https://openairdocs.org/incident/20041106029999A), Nov 6, 2004: Tcraft BC12D (N39971), Owanka, SD, Destroyed, 1 fatal. (-23) The student pilot was flying over his property and was returning for a landing just before sundown when the accident occurred. The pilot's son witnessed…

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.