# Accident 20010712015599A: Tcraft F21B, Simsbury, CT, July 12, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 12, 2001, 07:45 local time
- Place: Simsbury, CT
- Airport: Simsbury Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 41.8796° N, 72.8095° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=41.8796&lon=-72.8095&mi=10
- Aircraft: N4418U, registered now (https://openairdocs.org/aircraft/N4418U) (OpenAirDocs)
- Registry model: Taylorcraft F21B (registry code 8850909, https://openairdocs.org/model/taylorcraft-f21b) (OpenAirDocs)
- Reported make and model: TCRAFT F21B
- Reported engine: LYC O235L2C
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 8,650 total, 50 in this make and model, 100 in the last 90 days
- NTSB investigation: [NTSB NYC01LA170](https://openairdocs.org/ntsb/NYC01LA170) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010712015599A

## Narrative

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

(.19) ON JULY 12, 2001, ABOUT 0745 EASTERN DAYLIGHT TIME, A TAYLORCRAFT F21B, N4418U, WAS SUBSTANTIALLY DAMAGED WHILE LANDING AT THE SIMSBURY AIRPORT, SIMSBURY, CONNECTICUT. THE CERTIFICATED FLIGHT INSTRUCTOR (CFI) AND STUDENT PILOT WERE NOT INJURED.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED FOR THE LOCAL INSTRUCTIONAL FLIGHT CONDUCTED UNDER 14 CFR PART 91.  ACCORDING TO A FEDERAL AVIATION ADMINISTRATION INSPECTOR, THE AIRPLANE WAS EXECUTING TOUCH AND GO'S ON RUNWAY 03, A 2,205 FOOT LONG, 50 FOOT WIDE, ASPHALT RUNWAY.  AFTER TOUCHDOWN, THE AIRPLANE GROUND LOOPED, NOSED OVER, AND CAME TO REST INVERTED.  THE WINDS REPORTED AT A NEARBY AIRPORT, ABOUT THE TIME OF THE ACCIDENT, WERE FROM 320 DEGREES AT 10 KNOTS.  (-23) FOUND MAULE ANTI-SHIMMY CONNECTOR SPRINGS (HIGH AND LOW FREQUENCY SPRINGS) RIGGING LOOSE.  BOTH SPRINGS P/N 06-15150 WERE FOUND SLACK. RUDDER HORN TO RUDDER ATTACH BOLTS ALSO FOUND ELONGATED - 2" LEFT TO RIGHT PLAY AT RUDDER TRAILING EDGE BEFORE RESPONSE TO TAILWHEEL.                          (.4) ACCORDING TO THE CFI, THE PRIVATE PILOT WAS EXECUTING TOUCH AND GO'S ON RUNWAY 03. DURING THE THIRD LANDING, AFTER TOUCHDOWN, THE AIRPLANE'S TAIL WHEEL BEGAN TO "CHATTER." THE AIRPLANE STARTED TO VEER TO THE RIGHT AND DID NOT RESPOND TO LEFT RUDDER OR BRAKE INPUTS BY THE CFI, WHO HAD TAKEN OVER THE CONTROLS. THE AIRPLANE THEN DEPARTED THE RIGHT SIDE OF THE RUNWAY AND NOSED OVER. EXAMINATION OF THE AIRPLANE REVEALED THAT THE HIGH AND LOW FREQUENCY ANTI-SHIMMY COMPRESSION SPRINGS ON THE TAILWHEEL ASSEMBLY "HAD SLACK." THE "SLACK" ALLOWED FOR ABOUT 2 INCHES OF RUDDER MOVEMENT BEFORE THE COMPRESSION SPRINGS BECAME EFFECTIVE. REVIEW OF THE AIRPLANE'S MAINTENANCE RECORDS REVEALED THAT IT HAD SEVEN ANNUAL INSPECTIONS PERFORMED AFTER THE INSTALLATION OF THE TAILWHEEL ASSEMBLY. THE MOST RECENT ANNUAL INSPECTION WAS CONDUCTED ABOUT FOUR MONTHS PRIOR TO THE ACCIDENT, AND THE AIRPLANE HAD ACCUMULATED ABOUT 15 HOURS OF OPERATION SINCE. ACCORDING TO FAA REGULATIONS, APPENDIX D OF PART 43, SCOPE AND DETAIL OF ITEMS TO BE INCLUDED IN ANNUAL AND 100-HOUR INSPECTIONS, EACH PERSON PERFORMING AN ANNUAL OR 100-HOUR INSPECTION SHALL INSPECT ALL UNITS OF THE LANDING GEAR GROUP FOR POOR CONDITION AND INSECURITY OF ATTACHMENT. THE WINDS REPORTED AT A NEARBY AIRPORT, ABOUT THE TIME OF THE ACCIDENT, WERE FROM 320 DEGREES AT 10 KNOTS.

## 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 NYC01LA170](https://openairdocs.org/ntsb/NYC01LA170), Jul 12, 2001: Taylorcraft F21B (N4418U), Simsbury, CT, substantial damage. Probable cause: **This report was modified on 2/24/2016. Refer to the public docket for this accident for additional details.** a loose tail wheel assembly and the failure of maintenance personnel to adequately…

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.