# N3550X: Cessna 172S, registration cancelled 2012-11-08

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: November 8, 2012
- Status when cancelled: Registration expired, pending cancellation
- Airframe: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439)
- Data sheets: [TCDS 3A12](https://openairdocs.org/tcds/3A12) (OpenAirDocs)
- Serial number: 172S8894
- Type of aircraft: Fixed wing single engine
- Certificate issued: August 15, 2001
- Last registry action: August 31, 2004
- Mode S code: A3F9CE
- Owner when cancelled: [Dahlgren Steven W](https://openairdocs.org/faa-owner/DAHLGREN%20STEVEN%20W)
- Location: [Peoria, AZ](https://openairdocs.org/faa-place/AZ/Peoria)
- Owner type: Individual
- Owner's area on the map: 33.5723° N, 112.2481° W: Placed by OpenAirDocs at the center of ZIP code 85345, within about 2 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N3550X
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=3550X
- Page: https://openairdocs.org/deregistered/N3550X-2012-11-08

From the FAA registry file of October 29, 2026, cancelled registrations. Owners' street addresses are left out. The Mode S code belongs to the N-number, not the airframe.

ADs and bulletins for the Cessna 172S: https://openairdocs.org/model/cessna-172s.md

## NTSB investigations (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 LAX03LA091](https://openairdocs.org/ntsb/LAX03LA091), Feb 21, 2003: Cessna 172S (N3550X), Scottsdale, AZ, substantial damage. Probable cause: the student pilot's inadequate compensation for the existing crosswind conditions and failure to maintain directional control during the touch-and-go takeoff. A factor was his improper use of…

## FAA accident and incident reports (1)

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.

- [Accident 20030220002969A](https://openairdocs.org/incident/20030220002969A), Feb 20, 2003: Cessna 172S (N3550X), Scottsdale, AZ, Substantial damage. (.19) On February 20, 2003, at 1715 mountain standard time, a Cessna 172S, N3550X, collided with a hangar while attempting to do a touch-and-go takeoff from…

## Other aircraft with N3550X

- [Registered now](https://openairdocs.org/aircraft/N3550X): Verge X7, S/N P8DRLX71U4
- [Cancelled 1994-01-10](https://openairdocs.org/deregistered/N3550X-1994-01-10): Piper PA-31-310, S/N 318012022. Exported to Panama. Owner: [Giftos Dean](https://openairdocs.org/faa-owner/GIFTOS%20DEAN), [Nashua, NH](https://openairdocs.org/faa-place/NH/Nashua)
- [Cancelled 1970-06-25](https://openairdocs.org/deregistered/N3550X-1970-06-25): Mitsubishi MU-2B, S/N 018, built 1967. Owner: [Metropolitan Mooney Inc](https://openairdocs.org/faa-owner/METROPOLITAN%20MOONEY%20INC), [Teterboro, NJ](https://openairdocs.org/faa-place/NJ/Teterboro)

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