37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 252625 |
Time | |
Date | 199309 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : jnx |
State Reference | NC |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
Flight Phase | climbout : takeoff descent : approach landing other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 9 flight time total : 798 flight time type : 200 |
ASRS Report | 252625 |
Events | |
Anomaly | incursion : landing without clearance non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On sep/thu/93, I departed VFR from rdu at XA07Z to fly to W40 airport by way of jnall NDB. Jnall is the initial approach fix for the NDB runway 21 approach at jnx airport. My flight objective was to practice NDB navigation. I originally planned to fly to the jnall NDB and then proceed directly to W40. After arriving in the vicinity of jnall, I decided to fly the jnx NDB runway 21 procedure and conclude the procedure with a touch- and-go at jnx. During the touch-and-go at jnx, I noticed that runway 3's threshold had been displaced considerably from its normal position. This was due to construction underway at the airport. The displaced threshold reduced the length of runway 23 but not enough to close the runway to takeoffs and lndgs. After departing runway 21, I continued my flight to W40. Later, I found 2 NOTAMS referencing jnx airport that read: 1) jnx 3-21 southwest 1900 closed. 2) jnx 3-21 closed tgl. Prior to my flight, I had reviewed the NOTAMS pertaining to rdu and W40, but not the jnx NOTAMS because I had no intention at the time of landing there. An in-flight decision led to the impromptu touch-and-go on jnx runway 23. I thought later of how I could have avoided this situation. After I was airborne and decided to execute the NDB runway 21 approach at jnx, a call to flight service and a search of the NOTAMS would have revealed the touch-and-go restr at jnx. While this is a textbook solution, it is not customary, in my opinion, for pilots to contact flight service for NOTAM information before they make an unplanned stop at an airport on a good VFR day. Although runway 3's displaced threshold was visible from the air, all indications were that the airport was open for takeoff and lndgs which it was (except for touch-and-goes). There was no response to a call on the unicom during the NDB 21 approach. I have only a partial solution to offer for future consideration. Although no AWOS is installed at jnx, for airports with an AWOS facility, AWOS could be enhanced to provide NOTAM information in addition to WX reporting. This feature would provide pilots with real-time information about the airport environment, NAVAID integrity, procedural changes, etc.
Original NASA ASRS Text
Title: AN SMA PLT MADE A TOUCH-AND-GO LNDG ON A RWY CLOSED TO TOUCH-AND-GO LNDGS.
Narrative: ON SEP/THU/93, I DEPARTED VFR FROM RDU AT XA07Z TO FLY TO W40 ARPT BY WAY OF JNALL NDB. JNALL IS THE INITIAL APCH FIX FOR THE NDB RWY 21 APCH AT JNX ARPT. MY FLT OBJECTIVE WAS TO PRACTICE NDB NAV. I ORIGINALLY PLANNED TO FLY TO THE JNALL NDB AND THEN PROCEED DIRECTLY TO W40. AFTER ARRIVING IN THE VICINITY OF JNALL, I DECIDED TO FLY THE JNX NDB RWY 21 PROC AND CONCLUDE THE PROC WITH A TOUCH- AND-GO AT JNX. DURING THE TOUCH-AND-GO AT JNX, I NOTICED THAT RWY 3'S THRESHOLD HAD BEEN DISPLACED CONSIDERABLY FROM ITS NORMAL POS. THIS WAS DUE TO CONSTRUCTION UNDERWAY AT THE ARPT. THE DISPLACED THRESHOLD REDUCED THE LENGTH OF RWY 23 BUT NOT ENOUGH TO CLOSE THE RWY TO TKOFS AND LNDGS. AFTER DEPARTING RWY 21, I CONTINUED MY FLT TO W40. LATER, I FOUND 2 NOTAMS REFING JNX ARPT THAT READ: 1) JNX 3-21 SW 1900 CLOSED. 2) JNX 3-21 CLOSED TGL. PRIOR TO MY FLT, I HAD REVIEWED THE NOTAMS PERTAINING TO RDU AND W40, BUT NOT THE JNX NOTAMS BECAUSE I HAD NO INTENTION AT THE TIME OF LNDG THERE. AN INFLT DECISION LED TO THE IMPROMPTU TOUCH-AND-GO ON JNX RWY 23. I THOUGHT LATER OF HOW I COULD HAVE AVOIDED THIS SIT. AFTER I WAS AIRBORNE AND DECIDED TO EXECUTE THE NDB RWY 21 APCH AT JNX, A CALL TO FLT SVC AND A SEARCH OF THE NOTAMS WOULD HAVE REVEALED THE TOUCH-AND-GO RESTR AT JNX. WHILE THIS IS A TEXTBOOK SOLUTION, IT IS NOT CUSTOMARY, IN MY OPINION, FOR PLTS TO CONTACT FLT SVC FOR NOTAM INFO BEFORE THEY MAKE AN UNPLANNED STOP AT AN ARPT ON A GOOD VFR DAY. ALTHOUGH RWY 3'S DISPLACED THRESHOLD WAS VISIBLE FROM THE AIR, ALL INDICATIONS WERE THAT THE ARPT WAS OPEN FOR TKOF AND LNDGS WHICH IT WAS (EXCEPT FOR TOUCH-AND-GOES). THERE WAS NO RESPONSE TO A CALL ON THE UNICOM DURING THE NDB 21 APCH. I HAVE ONLY A PARTIAL SOLUTION TO OFFER FOR FUTURE CONSIDERATION. ALTHOUGH NO AWOS IS INSTALLED AT JNX, FOR ARPTS WITH AN AWOS FACILITY, AWOS COULD BE ENHANCED TO PROVIDE NOTAM INFO IN ADDITION TO WX RPTING. THIS FEATURE WOULD PROVIDE PLTS WITH REAL-TIME INFO ABOUT THE ARPT ENVIRONMENT, NAVAID INTEGRITY, PROCEDURAL CHANGES, ETC.
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.