OpenAirDocs.org

20030224004279I

Incident
Open the Markdown

FAA incident report · Cessna 172R · Baltimore, MD · February 24, 2003

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
February 24, 2003 · 16:58 local
Place
Baltimore, MD
Phase of flight
Normal Cruise
Operating rules
General operating rules (Part 91)
Aircraft
N35331
Reported as
Cessna 172R
Pilot’s flight hours
1,500 total650 in this make and model150 in the last 90 days
N35331Registration cancelled Jan 6, 2014 · Cessna 172RS/N 17281037 · Built 2001Airframe modelCessna 172REngine modelLycoming I0360 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) On 24 feb 03, I was monitoring and training a student pilot on a cross country training/refresher flight from frederick, MD to lancaster, pa and return. The VFR flight included clearview airpark as the first navigation check point. Recent snow storms made visual navigation very difficult and the student pilot was unable to clearly identify clearview airpark, his first check point. The student decided to head directly to the next check point which was lancaster pa. When I looked at the student pilots flight plan, I realized that the student pilot had turned to the wrong heading (098), it was obviously the wrong heading. The correct heading, from clearview to lancaster was 047 degrees. Turning to the wrong heading was compounded by an approximate 50 kt tailwind from the west. Very shortly (less than a minute) after turning to the wrong heading, I told the student pilot to turn to a northerly heading immediately to avoid inadvertent adiz penetration. But due to the strong tailwinds the aircraft had already entered the adiz. Incident closed.

As the FAA filed it

(-23) ON 24 FEB 03, I WAS MONITORING AND TRAINING A STUDENT PILOT ON A CROSS COUNTRY TRAINING/REFRESHER FLIGHT FROM FREDERICK, MD TO LANCASTER, PA AND RETURN. THE VFR FLIGHT INCLUDED CLEARVIEW AIRPARK AS THE FIRST NAVIGATION CHECK POINT. RECENT SNOW STORMS MADE VISUAL NAVIGATION VERY DIFFICULT AND THE STUDENT PILOT WAS UNABLE TO CLEARLY IDENTIFY CLEARVIEW AIRPARK, HIS FIRST CHECK POINT. THE STUDENT DECIDED TO HEAD DIRECTLY TO THE NEXT CHECK POINT WHICH WAS LANCASTER PA. WHEN I LOOKED AT THE STUDENT PILOTS FLIGHT PLAN, I REALIZED THAT THE STUDENT PILOT HAD TURNED TO THE WRONG HEADING (098), IT WAS OBVIOUSLY THE WRONG HEADING. THE CORRECT HEADING, FROM CLEARVIEW TO LANCASTER WAS 047 DEGREES. TURNING TO THE WRONG HEADING WAS COMPOUNDED BY AN APPROXIMATE 50 KT TAILWIND FROM THE WEST. VERY SHORTLY (LESS THAN A MINUTE) AFTER TURNING TO THE WRONG HEADING, I TOLD THE STUDENT PILOT TO TURN TO A NORTHERLY HEADING IMMEDIATELY TO AVOID INADVERTENT ADIZ PENETRATION. BUT DUE TO THE STRONG TAILWINDS THE AIRCRAFT HAD ALREADY ENTERED THE ADIZ. INCIDENT CLOSED.