A climbing BE99 has an near midair collision with a crossing piper that was supposed to be 500 ft above his altitude 20 mi east of msn, wi.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	467373
Time
Date	200003
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : msn.airport
State Reference	WI
Altitude	msl bound lower : 4000 msl bound upper : 4500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : msn.tracon
Operator	common carrier : air taxi
Make Model Name	Airliner 99
Operating Under FAR Part	Part 135
Flight Phase	climbout : intermediate altitude
Route In Use	departure : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : msn.tracon
Operator	general aviation : personal
Make Model Name	Piper Aircraft Corp Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	cruise : level
Route In Use	enroute : direct
Flight Plan	None
Person 1
Affiliation	company : air taxi
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 5000 flight time type : 2000
ASRS Report	467373
Person 2
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	altitude deviation : excursion from assigned altitude altitude deviation : undershoot conflict : nmac non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued advisory
Consequence	faa : investigated
Miss Distance	horizontal : 100 vertical : 0
Supplementary
Problem Areas	ATC Human Performance Environmental Factor Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Upon departing msn, was told to level at 4000 ft due to traffic. Traffic was pointed out. I responded with aircraft in sight. The traffic was told to maintain 4500 ft. The aircraft did cross in front of me (right to left) at my altitude. I corrected to the right to resolve conflict. Asked controller what was going on. He responded that was the issued traffic. I said ok, but at my altitude. Controller, he is showing 4500 ft on the mdec. Controller asked the other aircraft what their altitude was with a current altitude setting. The controller said that he would write the incident up. After reviewing of incident do not know how to prevent this from occurring again. However, I initially thought that the problem may be with my altimeter. But, they (both) were set and verified on the ground with field elevation.

Original NASA ASRS Text

Title: A CLBING BE99 HAS AN NMAC WITH A XING PIPER THAT WAS SUPPOSED TO BE 500 FT ABOVE HIS ALT 20 MI E OF MSN, WI.

Narrative: UPON DEPARTING MSN, WAS TOLD TO LEVEL AT 4000 FT DUE TO TFC. TFC WAS POINTED OUT. I RESPONDED WITH ACFT IN SIGHT. THE TFC WAS TOLD TO MAINTAIN 4500 FT. THE ACFT DID CROSS IN FRONT OF ME (R TO L) AT MY ALT. I CORRECTED TO THE R TO RESOLVE CONFLICT. ASKED CTLR WHAT WAS GOING ON. HE RESPONDED THAT WAS THE ISSUED TFC. I SAID OK, BUT AT MY ALT. CTLR, HE IS SHOWING 4500 FT ON THE MDEC. CTLR ASKED THE OTHER ACFT WHAT THEIR ALT WAS WITH A CURRENT ALT SETTING. THE CTLR SAID THAT HE WOULD WRITE THE INCIDENT UP. AFTER REVIEWING OF INCIDENT DO NOT KNOW HOW TO PREVENT THIS FROM OCCURRING AGAIN. HOWEVER, I INITIALLY THOUGHT THAT THE PROB MAY BE WITH MY ALTIMETER. BUT, THEY (BOTH) WERE SET AND VERIFIED ON THE GND WITH FIELD ELEVATION.

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.