# Accident 20020209001409A: Amtr PULSAR, Prescott, AZ, February 9, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 9, 2002, 14:02 local time
- Place: Prescott, AZ
- Airport: Ernest A Love Field
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 34.4900° N, 112.4394° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.4900&lon=-112.4394&mi=10
- Aircraft: N3218N, a cancelled registration (https://openairdocs.org/deregistered/N3218N-2018-03-13) (OpenAirDocs)
- Registry model: Conrad William R PULSAR (registry code 05620XE, https://openairdocs.org/model/conrad-william-r-pulsar) (OpenAirDocs)
- Registry engine: Bombardier ROTAX (ALL) (registry code 09050, https://openairdocs.org/engine/bombardier-rotax-all) (OpenAirDocs)
- Reported make and model: AMTR PULSAR
- Pilot certificates: Student
- NTSB investigation: [NTSB LAX02LA081](https://openairdocs.org/ntsb/LAX02LA081) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020209001409A

## Narrative

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

(.19) ON FEBRUARY 9, 2002, AT 1402 MOUNTAIN STANDARD TIME, AN EXPERIMENTAL CONRAD PULSAR, N3218N, MADE A HARD LANDING AT PRESCOTT, ARIZONA. THE PILOT/OWNER WAS OPERATING THE AIRPLANE UNDER THE PROVISIONS OF 14 CFR PART 91. THE STUDENT PILOT AND THE SECOND PILOT, WHO HELD A COMMERCIAL CERTIFICATE, WERE NOT INJURED. THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE. THE PERSONAL LOCAL FLIGHT DEPARTED PRESCOTT ABOUT 1350. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN HAD BEEN FILED. THE SAFETY BOARD INVESTIGATOR INTERVIEWED THE PILOT. THE PILOT STATED THAT HE HAD RECENTLY PURCHASED THE AIRPLANE AND THIS WAS HIS FIRST FLIGHT IN IT. HE HAD THE PREVIOUS OWNER SITTING IN THE RIGHT SEAT FOR THE FAMILIARIZATION FLIGHT. THE AIRPLANE HAD A SINGLE CONTROL STICK MOUNTED BETWEEN THE TWO SEATS, AND HE WAS THE SOLE MANIPULATOR OF THE CONTROLS. HE TOOK OFF AND INTENDED TO STAY IN THE TRAFFIC PATTER TO PRACTICE TOUCH-AND-GO LANDINGS. HE SAID THAT ON THE FIRST LANDING HE MADE A SHORT APPROACH THAT WAS TOO FAST. HE LANDED THE AIRPLANE HARD ON THE NOSE LANDING GEAR, WHICH COLLAPSED. THE AIRPLANE SLID ACROSS THE RUNWAY BEFORE COMING TO REST. THE PILOT SAID HE HAD ABOUT 100 HOURS TOTAL TIME IN AIRPLANES, PRIMARILY IN THE CESSNA 182. THIS WAS HIS FIRST FLIGHT IN THIS TYPE OF AIRPLANE. (-23) ON FEBRUARY 9, 2002, AT 1302 LOCAL, AN EXPERIMENTAL CONRAD PULSAR, N3218N, S/N173 MADE A HARD LANDING AT THE PRESCOTT AIRPORT. THE PILOT, A STUDENT PILOT WAS OPERATING THE AIRCRAFT UNDER PART 91. THE OWNER OF THE AIRCRAFT, WHO HOLDS A COMMERCIAL CERTIFICATE WITH NO CFI ENDORSEMENT, WAS IN THE RIGHT SEAT, AND WAS NOT INJURED. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE. THE PILOT MR. ELIAS STATED THAT HE HAD JUST PURCHASED THE AIRCRAFT AND WAS GETTING A CHECK OUT FROM THE PREVIOUS OWNER. THIS WAS HIS FIRST FLIGHT IN THE AIRCRAFT. THE AIRCRAFT HAD A SINGLE CONTROL STICK MOUNTED BETWEEN THE TWO SEATS, AND HE HAD SOLE CONTROL OF THE AIRCRAFT. THE AIRCRAFT TOOK OFF AND ENTERED THE TRAFFIC PATTERN TO PRACTICE TOUCH AND GO LANDINGS. THIS WAS THE FIRST LANDING. HE MADE A SHORT APPROACH THAT WAS TOO FAST. THE AIRCRAFT LANDED NOSE LOW, LANDING HARD AND THE NOSE GEAR COLLAPSED. IT PROCEEDED TO SLIDE ACROSS THE RUNWAY BEFORE COMING TO REST. THE PILOT AND PASSENGER EVACUATED THE AIRCRAFT.

## 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 LAX02LA081](https://openairdocs.org/ntsb/LAX02LA081), Feb 9, 2002: Conrad Pulsar 582 (N3218N), Prescott, AZ, substantial damage. Probable cause: The pilot failed to maintain landing reference speed and aircraft control. A factor was the gusty wind conditions.

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.