![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1284052 |
| Time | |
| Date | 201508 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | MAF.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Cessna Citation Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Route In Use | Visual Approach |
| Flight Plan | None |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 30 Flight Crew Total 4200 Flight Crew Type 550 |
| Person 2 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 35 Flight Crew Total 14500 Flight Crew Type 1450 |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Ground Incursion Runway |
Narrative:
After advising the controller of airport in sight and cancelling IFR flight plan; controller requested to squawk 1200 VFR code. We made a visual approach and landing to what we thought was odo airport. It was not until we had safely landed without any incident to anyone; that we realized that we had landed at maf instead of odo. At the time of our landing midland airport tower was closed. The flight was a 3:30 hour flight. We had left our hotel at XA00 local time for a XD00 departure however; the passengers showed up 2 hours late. It is my belief that fatigue was a contributing factor; as well as; accepting a visual in a non-familiar airport at night. Both airports have similar runway alignment and are within a close proximity to each other (odo rwy 34 and rwy 29) (maf rwy 34 and rwy 28). In the future when landing in a non-familiar airport day or night; I will not take a visual approach; instead; I will remain on instruments until positive identification of correct airport has been made or I will allow the controller to vector me to final.
Original NASA ASRS Text
Title: CE500 Flight Crew on an IFR flight to ODO; late at night; reports canceling IFR and accepting a visual approach. After landing they discover they have landed at MAF.
Narrative: After advising the Controller of airport in sight and cancelling IFR flight plan; Controller requested to squawk 1200 VFR code. We made a visual approach and landing to what we thought was ODO airport. It was not until we had safely landed without any incident to anyone; that we realized that we had landed at MAF instead of ODO. At the time of our landing Midland Airport Tower was closed. The flight was a 3:30 hour flight. We had left our hotel at XA00 local time for a XD00 departure however; the passengers showed up 2 hours late. It is my belief that fatigue was a contributing factor; as well as; accepting a visual in a non-familiar airport at night. Both airports have similar runway alignment and are within a close proximity to each other (ODO Rwy 34 and Rwy 29) (MAF Rwy 34 and Rwy 28). In the future when landing in a non-familiar airport day or night; I will not take a visual approach; instead; I will remain on instruments until positive identification of correct airport has been made or I will allow the controller to vector me to final.
Data retrieved from NASA's ASRS site 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.