# Accident 19980921037701A: Amtr SEAFURYTMK20, Reno, NV, September 21, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 21, 1998, 09:45 local time
- Place: Reno, NV
- Airport: Reno/Stead Airport
- Collision: Midair collision, first aircraft
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: General operating rules (Part 91)
- Location: 39.7093° N, 119.8209° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.7093&lon=-119.8209&mi=10
- Aircraft: N24SF, registered now (https://openairdocs.org/aircraft/N24SF) (OpenAirDocs)
- Registry model: Hawker SEA FURY F B II (registry code 4220200, https://openairdocs.org/model/hawker-sea-fury-f-b-ii) (OpenAirDocs)
- Registry engine: Wright R3350-32WA (registry code 67042, https://openairdocs.org/engine/wright-r3350-32wa) (OpenAirDocs)
- Reported make and model: AMTR SEAFURYTMK20
- Reported engine: WRIGHT R3350*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 17,810 total, 107 in this make and model
- NTSB investigation: [NTSB LAX98LA302](https://openairdocs.org/ntsb/LAX98LA302) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980921037701A

## Narrative

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

(-23)AIRCRAFT OVER RAN A LANCAIR IV ON TAXI TO RUNWAY. PILOT SAID HE NEVER SAW THE SMALLER AIRCRAFT.  PILOT HAD JUST TACIED PAST AT LEAST 3 F-16'S AND A F-18 THAT WHERE IN IDLE AND WAS FIGHTING JET BLAST.  THE TOWER WAS IN OPERATION.ON SEPTEMBER 21, 1998, AT 0945 HOURS PACIFIC STANDARD TIME, A BOGNUDA LIVIO IV LANCAIR, N805L, WAS SUBSTANTIALLY DAMAGED WHEN A HAWKER SIDDELEY SEA FURY TMK 20, N24SF, TAXIED INTO ITS EMPENNAGE WHILE IT WAS HOLDING ON THE TAXIWAY AWAITING TAKEOFF AT THE RENO STEAD AIRPORT, RENO, NEVADA. THE SEAL FURY TMK 20 SUSTAINED NO DAMAGE. NO INJURIES WERE SUSTAINED BY THE PRIVATE PILOT OF THE SEA FURY TMK 20. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE PERSONAL FLIGHTS. THE PILOT OF THE LANCAIR REPORTED THAT HE STOPPED ON THE TAXIWAY ABOUT 500 TO 600 FEET FROM THE RUNWAY END BECAUSE THE TOWER ADVISED HIM OF WAKE TURBULENCE BEHIND A MILITARY C-130 AIRCRAFT STOPPED ON THE TAXIWAY IN FRONT OF HIM. HE REMAINED STOPPED IN THAT POSITION FOR 5 TO 10 MINUTES WHEN, WITHOUT WARNING THE SEA FURY TAXIED INTO THE EMPENNAGE. THE PILOT OF THE TAIL WHEEL EQUIPPED SEA FURY REPORTED THAT HE RECEIVED CLEARANCE TO TAXI TO RUNWAY 26. HE SAW THE C-130 AHEAD BUT WAS NEVER TOLD   OF THE PRESENCE OF THE SMALLER LANCAIR. THE RENO AIR RACES HAD FINISHED THE PREVIOUS DAY AND SEVERAL VISITING MILITARY JETS WITH THEIR ENGINES OPERATING WERE ALSO PREPARING TO DEPART. THE MILITARY JETS WERE PARKED EDJACENT TO THE TAXIWAY WITH THEIR JET EXHAUST BLOWING ACROSS THE TAXIWAY, WHICH MADE IT DIFFICULT FOR THE SEA FURY PILOT TO S-TURN AS HE TAXIED BEHIND THEM. THE SEA FURY PILOT REPORTED HE NEVER SAW THE LANCAIR PRIOR TO THE COLLISION.

## Other aircraft in the event

- N805L, Amtr LANCAIRIV: [Accident 19980921037702A](https://openairdocs.org/incident/19980921037702A)

## 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 LAX98LA302](https://openairdocs.org/ntsb/LAX98LA302), Sep 21, 1998: Hawker Siddeley SEA Fury TMK 20 (N24SF), Reno, NV, no damage. Probable cause: The failure of the pilot-in-command to maintain adequate visual surveillance of the taxiway in front of his aircraft to avoid the collision.

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.