37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 193461 |
Time | |
Date | 199110 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : 6b6 |
State Reference | MA |
Altitude | agl bound lower : 4 agl bound upper : 4 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | landing other |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 3 flight time total : 680 flight time type : 3 |
ASRS Report | 193461 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Events | |
Anomaly | conflict : ground critical conflict : nmac other anomaly other |
Independent Detector | other other : unspecified cockpit |
Resolutory Action | flight crew : took evasive action |
Consequence | other |
Miss Distance | horizontal : 50 vertical : 50 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I have landed at minute man several times in the past but always approaching from the east or northeast. This day I flew in from the west, called unicom for the advisory and set myself up for what I thought was the left downwind for 21, then left base and final, calling my actions on unicom throughout the pattern. As I began my flare to land, I noticed opposite direction traffic on final for the correct 21. I was, in fact, landing on 3 which was unmarked. I immediately executed a go around steering to the right of the runway over the grass. The opposite direction traffic went by high and to my left. As I was in full power, flaps down confign approximately 4 ft AGL, a wooden saw horse was in my flight path consequently striking it with my aircraft propeller. Avoiding the saw horse was impossible due to a row of parked aircraft farther to the right or the unknown flight path of the opposite direction traffic on the left. After the strike, my aircraft climbed out of the airfield normally. I then elected to land at nearby hanscom field, which is my home base, to assess damage to the aircraft. There were no personal injuries. I firmly believe a contributing factor to the accident and near miss was the absence of the runway direction number which should have been painted on the approach end of 3 to warn me or anyone else of a possible error in landing. I also feel someone at the airfield was negligent in allowing a wooden saw horse to be out in the open near an active runway. After landing at hanscom I called manager at FBO aviation to advise him of the incident. He then informed me the runway direction number 3 was removed for some reason. Callback conversation with reporter revealed the following information: reporter states the gentleman he spoke with was vague about the reason the numbers were removed. Construction or something. He stated when questioned that he did not overfly the airport to check traffic. Then informed analyst 'oh, there was no traffic, just the 1 plane'! Blamed incident on his own complacency, because he had flown into this airport before. Analyst agrees with major complacency.
Original NASA ASRS Text
Title: PLT LINES UP FOR WRONG RWY FOR LNDG. ALMOST MEETS OPPOSITE DIRECTION TFC ALSO LNDG.
Narrative: I HAVE LANDED AT MINUTE MAN SEVERAL TIMES IN THE PAST BUT ALWAYS APCHING FROM THE E OR NE. THIS DAY I FLEW IN FROM THE W, CALLED UNICOM FOR THE ADVISORY AND SET MYSELF UP FOR WHAT I THOUGHT WAS THE L DOWNWIND FOR 21, THEN L BASE AND FINAL, CALLING MY ACTIONS ON UNICOM THROUGHOUT THE PATTERN. AS I BEGAN MY FLARE TO LAND, I NOTICED OPPOSITE DIRECTION TFC ON FINAL FOR THE CORRECT 21. I WAS, IN FACT, LNDG ON 3 WHICH WAS UNMARKED. I IMMEDIATELY EXECUTED A GAR STEERING TO THE R OF THE RWY OVER THE GRASS. THE OPPOSITE DIRECTION TFC WENT BY HIGH AND TO MY L. AS I WAS IN FULL PWR, FLAPS DOWN CONFIGN APPROX 4 FT AGL, A WOODEN SAW HORSE WAS IN MY FLT PATH CONSEQUENTLY STRIKING IT WITH MY ACFT PROP. AVOIDING THE SAW HORSE WAS IMPOSSIBLE DUE TO A ROW OF PARKED ACFT FARTHER TO THE R OR THE UNKNOWN FLT PATH OF THE OPPOSITE DIRECTION TFC ON THE L. AFTER THE STRIKE, MY ACFT CLBED OUT OF THE AIRFIELD NORMALLY. I THEN ELECTED TO LAND AT NEARBY HANSCOM FIELD, WHICH IS MY HOME BASE, TO ASSESS DAMAGE TO THE ACFT. THERE WERE NO PERSONAL INJURIES. I FIRMLY BELIEVE A CONTRIBUTING FACTOR TO THE ACCIDENT AND NEAR MISS WAS THE ABSENCE OF THE RWY DIRECTION NUMBER WHICH SHOULD HAVE BEEN PAINTED ON THE APCH END OF 3 TO WARN ME OR ANYONE ELSE OF A POSSIBLE ERROR IN LNDG. I ALSO FEEL SOMEONE AT THE AIRFIELD WAS NEGLIGENT IN ALLOWING A WOODEN SAW HORSE TO BE OUT IN THE OPEN NEAR AN ACTIVE RWY. AFTER LNDG AT HANSCOM I CALLED MGR AT FBO AVIATION TO ADVISE HIM OF THE INCIDENT. HE THEN INFORMED ME THE RWY DIRECTION NUMBER 3 WAS REMOVED FOR SOME REASON. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE GENTLEMAN HE SPOKE WITH WAS VAGUE ABOUT THE REASON THE NUMBERS WERE REMOVED. CONSTRUCTION OR SOMETHING. HE STATED WHEN QUESTIONED THAT HE DID NOT OVERFLY THE ARPT TO CHK TFC. THEN INFORMED ANALYST 'OH, THERE WAS NO TFC, JUST THE 1 PLANE'! BLAMED INCIDENT ON HIS OWN COMPLACENCY, BECAUSE HE HAD FLOWN INTO THIS ARPT BEFORE. ANALYST AGREES WITH MAJOR COMPLACENCY.
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.