DFW07LA082 · Cessna T210R
Cessna T210R and Cessna 172K · Accident: midair collision on approach
Event
- NTSB case
- DFW07LA082
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Cessna T210R
- Aircraft type
- Cessna 210
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N766DP
- Operator
- Robert K. Daniel Peterson · private individual
- Onboard fatalities
- Unknown
- Route
- From Boerne Stage Field (5C1), Boerne, TXTo Boerne Stage Field (5C1), Boerne, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Aircraft 2 · Cessna 172K
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N79286
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boerne Stage Field (5C1), Boerne, TXTo Boerne Stage Field (5C1), Boerne, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot of other aircraft › Clearance, not maintained
- Traffic pattern procedure › Improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While executing a go-around at an uncontrolled airport, a Cessna T210R airplane collided with a Cessna 172K airplane that was performing a touch and go landing to the same runway. The 9,100-hour pilot of the 172K reported that while preparing for takeoff on the touch and go he heard the T210R announce that he was going around. The 172K pilot then advised the T210R pilot again that he was performing a touch and go. While climbing out at approximately 50 feet above the runway the 172K pilot felt what he thought was a large bird strike. The 1,440-hour pilot of the T210R reported that, on short final, he realized he was going to overtake the 172K that had landed on the runway, and initiated a go-around at the approach end of the runway. Upon announcing his go-around on UNICOM he subsequently heard the 172K pilot state "touch and go" on the same frequency. At the same instant, the T210R pilot saw the 172K rise from below and fill up his windshield. He attempted an evasive maneuver to avoid a collision but contacted the tail section of the 172K. A witness on the ground confirmed these events, stating that the T210R rapidly gained speed on the 172K and climbed into him. The T210R impacted the 172K from the rear while climbing. The Cessna 172K sustained structural damage, while the damage to the T210R was limited to the propeller blades. None of the occupants on either aircraft was injured. The visibility at the time of the collision was reported as 10 statute miles.
Probable cause
The pilot's failure to maintain proper spacing during approach to landing and subsequent go-around, which resulted in a midair collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07LA082
- Event ID
- 20070320X00308
- Case number
- DFW07LA082
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1a80df6a2867a790d56765c6894ff4d48d479c019b947e71577e15e47ca9b5a3; retrieved 2026-09-22T04:00:16.485Z.