An atx operator flies into an airport under IFR flight plan but does not have current WX.

Attributes
ACN	412050
Time
Date	199808
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : blf
State Reference	WV
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 135
Flight Phase	climbout : takeoff landing other
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 5600 flight time type : 400
ASRS Report	412050
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On a 3 leg EMS (lifeguard) flight beginning in crw to blf, patient to be picked up in blf and transported to mgw. I filed IFR flight plan with lifeguard designation for first and second legs, which should have been for second leg only. Third leg (to crw) like the first would have been operating under part 91 while second leg would be far part 135. At the time of arrival at blf and mgw no WX observations were being taken. While the WX was as previously observed and forecast as being VFR, I requested a vector to intercept localizer and accepted clearance for an ILS at blf approach (contrary to 135.225). I did this just to help simplify the trip, because the WX was very good and I could have and should have filed a VFR flight plan only, thereby not being limited by part 135.225 and maybe other regulations. I did, however, have the latest reports which were less than 1 hour old, along with forecast for all airports involved. This may satisfy landing requirements by having latest information, but I am not sure and am in process of clarification.

Original NASA ASRS Text

Title: AN ATX OPERATOR FLIES INTO AN ARPT UNDER IFR FLT PLAN BUT DOES NOT HAVE CURRENT WX.

Narrative: ON A 3 LEG EMS (LIFEGUARD) FLT BEGINNING IN CRW TO BLF, PATIENT TO BE PICKED UP IN BLF AND TRANSPORTED TO MGW. I FILED IFR FLT PLAN WITH LIFEGUARD DESIGNATION FOR FIRST AND SECOND LEGS, WHICH SHOULD HAVE BEEN FOR SECOND LEG ONLY. THIRD LEG (TO CRW) LIKE THE FIRST WOULD HAVE BEEN OPERATING UNDER PART 91 WHILE SECOND LEG WOULD BE FAR PART 135. AT THE TIME OF ARR AT BLF AND MGW NO WX OBSERVATIONS WERE BEING TAKEN. WHILE THE WX WAS AS PREVIOUSLY OBSERVED AND FORECAST AS BEING VFR, I REQUESTED A VECTOR TO INTERCEPT LOC AND ACCEPTED CLRNC FOR AN ILS AT BLF APCH (CONTRARY TO 135.225). I DID THIS JUST TO HELP SIMPLIFY THE TRIP, BECAUSE THE WX WAS VERY GOOD AND I COULD HAVE AND SHOULD HAVE FILED A VFR FLT PLAN ONLY, THEREBY NOT BEING LIMITED BY PART 135.225 AND MAYBE OTHER REGS. I DID, HOWEVER, HAVE THE LATEST RPTS WHICH WERE LESS THAN 1 HR OLD, ALONG WITH FORECAST FOR ALL ARPTS INVOLVED. THIS MAY SATISFY LNDG REQUIREMENTS BY HAVING LATEST INFO, BUT I AM NOT SURE AND AM IN PROCESS OF CLARIFICATION.

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.