# NTSB GAA16CA517: Jerant Frank Mong, N777FJ, Reno, NV, September 18, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 18, 2016, 08:35 local (15:35 UTC)
- Place: Reno, NV
- Coordinates: 39.662498, -119.868331 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.6625&lon=-119.8683&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining events: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report December 15, 2016
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 94100
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA517
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94100/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94100
- Page: https://openairdocs.org/ntsb/GAA16CA517

## Probable cause (aircraft 2)

The other pilot's failure to maintain adequate separation and visual lookout during landing, which resulted in his airplane colliding with the airplane ahead of it on the runway.

## Probable cause (aircraft 1)

The pilot's failure to maintain adequate separation and visual lookout during landing, which resulted in his airplane colliding with the airplane ahead of it on the runway.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 1; cases with it: [Jerant Frank MONG - JERANT RACER, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=05611KN), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Use of equip/info: use of policy/procedure](https://openairdocs.org/ntsb-findings/02063032): Personnel issues › Task performance · Flt operations/dispatcher, aircraft 1; cases with it: [Jerant Frank MONG - JERANT RACER, 1 case](https://openairdocs.org/ntsb-findings/02063032/cases.md?model=05611KN), [All aircraft, 191 cases](https://openairdocs.org/ntsb-findings/02063032/cases.md)
- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Tatelman-Pitts SPECIAL S-1, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=72202Q1), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Use of equip/info: use of policy/procedure](https://openairdocs.org/ntsb-findings/02063032): Personnel issues › Task performance · Flt operations/dispatcher, aircraft 2; cases with it: [Tatelman-Pitts SPECIAL S-1, 1 case](https://openairdocs.org/ntsb-findings/02063032/cases.md?model=72202Q1), [All aircraft, 191 cases](https://openairdocs.org/ntsb-findings/02063032/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event), aircraft 1; cases with it: [Jerant Frank MONG - JERANT RACER, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=05611KN), [All aircraft, 1,330 cases](https://openairdocs.org/ntsb-events/490/sequence.md)
- [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event), aircraft 2; cases with it: [Tatelman-Pitts SPECIAL S-1, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=72202Q1), [All aircraft, 1,330 cases](https://openairdocs.org/ntsb-events/490/sequence.md)

## Analysis (aircraft 2)

The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface.

## Analysis (aircraft 1)

The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface.

## Factual narrative (aircraft 2)

The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface.

## Factual narrative (aircraft 1)

The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface.

## Aircraft 1

- Registration: [N777FJ](https://openairdocs.org/aircraft/N777FJ), registered now, S/N FJ-1, built 2002 (OpenAirDocs)
- Reported make and model: Jerant Frank Mong (Jerant Ra)
- Registry model: [Jerant Frank MONG - JERANT RACER](https://openairdocs.org/model/jerant-frank-mong-jerant-racer) (registry code 05611KN) (OpenAirDocs)
- Registry engine: [Lycoming IO-360 series](https://openairdocs.org/engine/lycoming-io-360-series) (registry code 41881, reciprocating) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: FJ-1
- Year built: 2002
- Airframe hours: 155
- Engines: Lycoming IO-360-A16CD reciprocating
- Damage: Substantial damage
- Flight: Air race/show, Part 91
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, June 9, 2016
- Departed: RTS, Reno, NV
- Destination: RTS, Reno, NV
- Airport: RTS, Reno/Stead, runway 08, 7,608 × 150 ft, asphalt
- Equipment: Electronic primary flight display, Video recording device

## Aircraft 2

- Registration: [N767JW](https://openairdocs.org/aircraft/N767JW), registered now, S/N 7777, built 1971 (OpenAirDocs)
- Reported make and model: Tatelman-Pitts Special (S-1)
- Registry model: [Tatelman-Pitts SPECIAL S-1](https://openairdocs.org/model/tatelman-pitts-special-s-1) (registry code 72202Q1) (OpenAirDocs)
- Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: 7777
- Year built: 1971
- Airframe hours: 1096.5
- Engines: Lycoming O&OV-360 SER 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Air race/show, Part 91
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, August 15, 2016
- Departed: RTS, Reno, NV
- Destination: RTS, Reno, NV
- Airport: RTS, Reno/Stead, runway 08, 7,608 × 150 ft, asphalt
- Equipment: None

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N777FJ; age 51; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review May 3, 2016; seat: single; restraint: 5-point; flight hours: 2,392 total, 47.9 in this make and model, 2,298.6 as pilot in command, 27.3 in the last 90 days, 4.5 in the last 30 days
- Pilot, aircraft N767JW; age 35; injuries: none; airline transport, flight instructor; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review April 17, 2016; seat: single; restraint: 5-point; flight hours: 5,438 total, 292 in this make and model, 2,901 as pilot in command, 276 in the last 90 days, 78 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 59 °F, dew point 27 °F
- Altimeter: 30.21 inHg
- Observed at: KRTS

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20160918023202A](https://openairdocs.org/incident/20160918023202A), Sep 18, 2016: Jerant Frank MONG - JERANT RACER, Reno, NV, Substantial damage. During the national championship air races - N777FJ was landing in the number two position behind N767JW. N777FJ touched down and then began to oscillate.…

## Docket (4 files)

The files NTSB released with the investigation on November 8, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94100. 3.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (A) (item 1, .PDF, 713 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446256&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(A)-Master.PDF
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (B) (item 2, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446257&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(B)-Master.PDF
- Accident Photo (A) (item 3, .PDF, 1 photo, 520 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446258&FileExtension=.PDF&FileName=Accident%20Photo%20(A)-Master.PDF
- Accident Photo (B) (item 4, .PDF, 1 photo, 382 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446259&FileExtension=.PDF&FileName=Accident%20Photo%20(B)-Master.PDF

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.

---
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.