# Accident 19920215004602A: Cessna 172M, Sanford, ME, February 15, 1992

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 15, 1992, 09:30 local time
- Place: Sanford, ME
- Airport: Sanford Municipal
- Damage: Minor damage
- Collision: Midair collision, second aircraft
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: General operating rules (Part 91)
- Location: 43.3938° N, 70.7080° W: Placed by OpenAirDocs at , within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.3938&lon=-70.7080&mi=10
- Aircraft: N64147, registered now (https://openairdocs.org/aircraft/N64147) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: CONT O200A
- People aboard: 2
- Fatal injuries: 0
- NTSB investigation: [NTSB NYC92LA069](https://openairdocs.org/ntsb/NYC92LA069) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19920215004602A

## Narrative

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

WHILE BACK TAXIING ON RUNWAY AFTER LANDING COLLIDED WITH N6544G THAT WAS TURNING ONTO RUNWAY TO DEPART.DIDN'T YIELD

## Other aircraft in the event

- N6544G, Cessna 150L: [Accident 19920215004601A](https://openairdocs.org/incident/19920215004601A)

## 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 NYC92LA069](https://openairdocs.org/ntsb/NYC92LA069), Feb 15, 1992: Cessna 172M (N64147), Sanford, ME, minor damage. Probable cause: THE FAILURE OF THE PILOT OF N64147 TO MAINTAIN ADEQUATE SPACING AND VISUAL LOOKOUT FROM N6544G WHILE TAXIING, RESULTING IN A GROUND 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.