Narrative:

I was taking off with a load of 3 skydivers for the first jump of the day at an established parachute center. Prior to takeoff, I had my radio on for more than 5 mins while I let my engine warm up and performed my runup. I heard no calls from inbound traffic during this time. I announced my departure on CTAF, looked for traffic in the pattern, and took off on runway 33. At 500 ft AGL, while maintaining runway heading, I began my power reduction. I looked down as I brought back my manifold pressure. I looked up before adjusting my RPM and suddenly saw a small twin engine aircraft passing above me in the opposite direction. It was approximately 200 ft or less above me and 50 ft to my right. One of the jumpers in my aircraft saw the twin and agreed with my estimate of the distance. I called out on CTAF 'twin over napoleon, did you see me?' there was no response. I tried again to establish contact with the twin with no success. As I continued climbing, I turned left to look for the twin. I saw it flying low over a small narrow lake less than 1 mi southwest of the airport. At 2000 ft MSL, I contacted lansing approach as normal. I then asked if they were working the twin that was now heading northwest toward jackson airport. I was told they were not in communication with him and didn't have him on radar. I informed them of the near midair. I then tuned communication #2 to jackson tower and followed the twin toward jackson. I heard him contact the tower and get clearance to land on runway 31. After watching him land and begin his taxi back, I called the tower. I idented myself, asked for the full registration number of the twin, and the tower gave it to me. Tower also told me the aircraft was from the local community college and was taking children on a fly-by of their summer camp. I explained what happened and asked tower if they could please inform the pilot about the near midair collision and advise him to use the CTAF when flying near the airport. Tower told me they would do so. Contributing factors to this near midair collision were my high nose up attitude during initial climb out immediately after takeoff. This restr my forward vision. To the best of my knowledge, the twin was not monitoring the CTAF of the airport he was flying over. In discussion with personnel at the airport after I landed, I was told that the twin flew directly over the airport about 500 ft AGL in a turn. He was also well below the pattern altitude and passing through the departure area of the runway. He was apparently taking a direct route from his departure airport and turning a right base to final over my departure airport in order to make his pass down the lake in front of the children's summer camp. Corrective action on my part would include increased vigilance during the takeoff phase of the flight. Corrective action for the twin pilot would be to monitor the local frequency whenever near an airport and to never fly below the pattern altitude unless he is in the act of takeoff or landing.

Google
 

Original NASA ASRS Text

Title: PLT OF A C182 JUMP ACFT HAS NMAC WITH PA34-200 ON INITIAL CLB FROM NON TWR ARPT. THE PA34 WAS FLYING DIRECTLY OVER THE ARPT AT 500 FT TAKING CHILDREN TO SEE THEIR SUMMER CAMP.

Narrative: I WAS TAKING OFF WITH A LOAD OF 3 SKYDIVERS FOR THE FIRST JUMP OF THE DAY AT AN ESTABLISHED PARACHUTE CTR. PRIOR TO TKOF, I HAD MY RADIO ON FOR MORE THAN 5 MINS WHILE I LET MY ENG WARM UP AND PERFORMED MY RUNUP. I HEARD NO CALLS FROM INBOUND TFC DURING THIS TIME. I ANNOUNCED MY DEP ON CTAF, LOOKED FOR TFC IN THE PATTERN, AND TOOK OFF ON RWY 33. AT 500 FT AGL, WHILE MAINTAINING RWY HDG, I BEGAN MY PWR REDUCTION. I LOOKED DOWN AS I BROUGHT BACK MY MANIFOLD PRESSURE. I LOOKED UP BEFORE ADJUSTING MY RPM AND SUDDENLY SAW A SMALL TWIN ENG ACFT PASSING ABOVE ME IN THE OPPOSITE DIRECTION. IT WAS APPROX 200 FT OR LESS ABOVE ME AND 50 FT TO MY R. ONE OF THE JUMPERS IN MY ACFT SAW THE TWIN AND AGREED WITH MY ESTIMATE OF THE DISTANCE. I CALLED OUT ON CTAF 'TWIN OVER NAPOLEON, DID YOU SEE ME?' THERE WAS NO RESPONSE. I TRIED AGAIN TO ESTABLISH CONTACT WITH THE TWIN WITH NO SUCCESS. AS I CONTINUED CLBING, I TURNED L TO LOOK FOR THE TWIN. I SAW IT FLYING LOW OVER A SMALL NARROW LAKE LESS THAN 1 MI SW OF THE ARPT. AT 2000 FT MSL, I CONTACTED LANSING APCH AS NORMAL. I THEN ASKED IF THEY WERE WORKING THE TWIN THAT WAS NOW HDG NW TOWARD JACKSON ARPT. I WAS TOLD THEY WERE NOT IN COM WITH HIM AND DIDN'T HAVE HIM ON RADAR. I INFORMED THEM OF THE NEAR MIDAIR. I THEN TUNED COM #2 TO JACKSON TWR AND FOLLOWED THE TWIN TOWARD JACKSON. I HEARD HIM CONTACT THE TWR AND GET CLRNC TO LAND ON RWY 31. AFTER WATCHING HIM LAND AND BEGIN HIS TAXI BACK, I CALLED THE TWR. I IDENTED MYSELF, ASKED FOR THE FULL REGISTRATION NUMBER OF THE TWIN, AND THE TWR GAVE IT TO ME. TWR ALSO TOLD ME THE ACFT WAS FROM THE LCL COMMUNITY COLLEGE AND WAS TAKING CHILDREN ON A FLY-BY OF THEIR SUMMER CAMP. I EXPLAINED WHAT HAPPENED AND ASKED TWR IF THEY COULD PLEASE INFORM THE PLT ABOUT THE NMAC AND ADVISE HIM TO USE THE CTAF WHEN FLYING NEAR THE ARPT. TWR TOLD ME THEY WOULD DO SO. CONTRIBUTING FACTORS TO THIS NMAC WERE MY HIGH NOSE UP ATTITUDE DURING INITIAL CLBOUT IMMEDIATELY AFTER TKOF. THIS RESTR MY FORWARD VISION. TO THE BEST OF MY KNOWLEDGE, THE TWIN WAS NOT MONITORING THE CTAF OF THE ARPT HE WAS FLYING OVER. IN DISCUSSION WITH PERSONNEL AT THE ARPT AFTER I LANDED, I WAS TOLD THAT THE TWIN FLEW DIRECTLY OVER THE ARPT ABOUT 500 FT AGL IN A TURN. HE WAS ALSO WELL BELOW THE PATTERN ALT AND PASSING THROUGH THE DEP AREA OF THE RWY. HE WAS APPARENTLY TAKING A DIRECT RTE FROM HIS DEP ARPT AND TURNING A R BASE TO FINAL OVER MY DEP ARPT IN ORDER TO MAKE HIS PASS DOWN THE LAKE IN FRONT OF THE CHILDREN'S SUMMER CAMP. CORRECTIVE ACTION ON MY PART WOULD INCLUDE INCREASED VIGILANCE DURING THE TKOF PHASE OF THE FLT. CORRECTIVE ACTION FOR THE TWIN PLT WOULD BE TO MONITOR THE LCL FREQ WHENEVER NEAR AN ARPT AND TO NEVER FLY BELOW THE PATTERN ALT UNLESS HE IS IN THE ACT OF TKOF OR LNDG.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.