On 3 May 2006 08:33:30 -0700, "rps" wrote in
.com::
I was close to exchanging paint with a colorful,
small plane that approached me from the west and maybe 100 feet lower.
It appears that your Near Midair Collision should be reported:
http://www.faa.gov/ATpubs/AIM/AIM.pdf
7-6-3. Near Midair Collision Reporting
a. Purpose and Data Uses. The primary purpose
of the Near Midair Collision (NMAC) Reporting
Program is to provide information for use in
enhancing the safety and efficiency of the National
Airspace System. Data obtained from NMAC reports
are used by the FAA to improve the quality of FAA
services to users and to develop programs, policies,
and procedures aimed at the reduction of NMAC
occurrences. All NMAC reports are thoroughly
investigated by Flight Standards Facilities in
coordination with Air Traffic Facilities. Data from
these investigations are transmitted to FAA Headquarters
in Washington, DC, where they are compiled
and analyzed, and where safety programs and
recommendations are developed.
b. Definition. A near midair collision is defined
as an incident associated with the operation of an
aircraft in which a possibility of collision occurs as a
result of proximity of less than 500 feet to another
aircraft, or a report is received from a pilot or a flight
crew member stating that a collision hazard existed
between two or more aircraft.
c. Reporting Responsibility. It is the responsibility
of the pilot and/or flight crew to determine
whether a near midair collision did actually occur
and, if so, to initiate a NMAC report. Be specific, as
ATC will not interpret a casual remark to mean that
a NMAC is being reported. The pilot should state “I
wish to report a near midair collision.”
AIM 2/16/06
7-6-3 Safety, Accident, and Hazard Reports
d. Where to File Reports. Pilots and/or flight
crew members involved in NMAC occurrences are
urged to report each incident immediately:
1. By radio or telephone to the nearest FAA ATC
facility or FSS.
2. In writing, in lieu of the above, to the nearest
Flight Standards District Office (FSDO).
e. Items to be Reported.
1. Date and time (UTC) of incident.
2. Location of incident and altitude.
3. Identification and type of reporting aircraft,
aircrew destination, name and home base of pilot.
4. Identification and type of other aircraft,
aircrew destination, name and home base of pilot.
5. Type of flight plans; station altimeter setting
used.
6. Detailed weather conditions at altitude or
flight level.
7. Approximate courses of both aircraft:
indicate if one or both aircraft were climbing or
descending.
8. Reported separation in distance at first
sighting, proximity at closest point horizontally and
vertically, and length of time in sight prior to evasive
action.
9. Degree of evasive action taken, if any (from
both aircraft, if possible).
10. Injuries, if any.
f. Investigation. The FSDO in whose area the
incident occurred is responsible for the investigation
and reporting of NMACs.
g. Existing radar, communication, and weather
data will be examined in the conduct of the
investigation. When possible, all cockpit crew
members will be interviewed regarding factors
involving the NMAC incident. Air traffic controllers
will be interviewed in cases where one or more of the
involved aircraft was provided ATC service. Both
flight and ATC procedures will be evaluated. When
the investigation reveals a violation of an FAA
regulation, enforcement action will be pursued.
---------------------
§ 91.111 Operating near other aircraft.
(a) No person may operate an aircraft so close to another aircraft as
to create a collision hazard.