# Incident 20000325020389I: Amtr VIPER, Tulsa, OK, March 25, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 25, 2000, 14:00 local time
- Place: Tulsa, OK
- Airport: Richard Lloyd Jones Jr Airport
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 36.1540° N, 95.9928° W: Placed by OpenAirDocs: center of Tulsa, OK, within about 8 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1540&lon=-95.9928&mi=10
- Aircraft: N6227S, a cancelled registration (https://openairdocs.org/deregistered/N6227S-2015-05-19) (OpenAirDocs)
- Registry model: Daunay Brice VIPER (registry code 0560479, https://openairdocs.org/model/daunay-brice-viper) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMTR VIPER
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 201 total, 100 in this make and model, 32 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000325020389I

## Narrative

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

(-23)THE PILOT JUST PURCHASED THE AIRCRAFT AND HAD TAKEN IT OUT TO FAMILIARIZE HIMSELF WITH IT. HE HAD 100 HOURS IN THIS TYPE AIRCRAFT. AFTER FLYING LOCALLY AND PERFORMING TWO TOUCH AND GO'S, THE PILOT WAS GOING TO COME TO A FULL STOP TO REFUEL IN PREPARATION FOR A CROSS COUNTRY FLIGHT.  HE STATED THAT HE HAD THREE GREEN LIGHTS, BUT THAT THE NOSE GEAR WAS NOT DOWN.  THE NOSE SETTLED TO THE GROUND AS THE AIRCRAFT SLOWED.  DAMAGE TO THE AIRCRAFT WAS MINOR, (FIBERGLASS ON NOSE GROUND AWAY).  THE LANDING GEAR SYSTEM WAS INSPECTED AND A DOWN ON THE GEAR WAS FOUND OUT AF ADJUSTMENT AND REPAIRED.  THE FIBERGLASS ON THE NOSE WAS REPAIRED AND THE AIRCRAFT WAS FLOWN TO THE  NEW OWNERS HOME IN ^PRIVACY DATA O^, ON 03/25/00.

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.