Aircraft that carried N2663A · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N2663A now.
NTSB investigations on N2663A · 3
Of this N-number, whichever aircraft carried it.
NTSB LAX05CA212Accident · No injuriesData collectionFinal reportPiper PA-18-135 · Pine Valley, CAThe pilot's delay in aborting the takeoff and excessive brake application. A contributing factor was the downsloping terrain used for the landing and takeoff.NTSB LAX82DA211Accident · No injuriesFinal reportPiper PA-18 · Colusa, CAThe pilot reported that during a 3-point landing in calm wind conditions, the aircraft veered to the right as soon as the main gear touched down. The pilot stated that he applied full left rudder and brake, but to no avail. The plane continued to the right…NTSB LAX80DVG08Accident · No injuriesClosedPiper PA-18 · Colusa, CA
FAA incident reports on N2663A · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20050619010909APiper PA18135 · Pine Valley, CA(-23) N2663A, a PA-18-135, departed gillespie field (see) on 6/19/05 with one individual on board. Approximately 2 miles west of Pine Valley, California, the pilot observed a dirt landing strip. He attempted to execute a touch and go landing. After touch…Accident 19820607020849APiper PA18 · Colusa, CAPilot lost directional control during landing on narrow Private runway.Accident 19791201033369APiper PA18135 · Colusa, CAPilot was flying low inspecting fences. Hit a power line.