37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 829361 |
Time | |
Date | 200903 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | XSA.Airport |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb Initial Approach Cruise |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 375 Flight Crew Type 75 |
Events | |
Anomaly | Other PIRED Accuracy |
Narrative:
Pilot in command experienced heavy turbulence and LLWS at xsa; as well as enroute back to flight point of origin at 2w6. Pilot in command called FSS at the conclusion of the flight to submit a PIREP to advise other GA aircraft in the vicinity of potentially hazardous turbulence. The first PIREP submitted was submitted as a uua PIREP; describing heavy turbulence and possible LLWS during final approach and landing at xsa. The second PIREP was a ua code; concerning moderate to severe turbulence at about the pxt 240 degree radial at 15 NM at 3;000 ft MSL. The pilot in command has a habit of verifying if the PIREP was entered correctly by means of using both adds and duat. Upon checking both sites; all that was seen (a query for PIREPS submitted over the last 6 hours was used) was a ua PIREP at the pxt 240 degree radial at 5 NM; a P28R reporting light chop. The uua PIREP submitted for the hazardous conditions at xsa was not entered by the FSS representative. This; in the opinion of the pilot in command; represents a potential safety of flight hazard. It is the opinion of the pilot in command that there should be a mechanism for reporting PIREPS outside of ATC and FSS. It would be prudent that a website be created or a mechanism within duat/duats be created to allow pilots to submit PIREPS electronically. This would encourage more pilot weather reporting and contribute to increased flight safety.
Original NASA ASRS Text
Title: General aviation pilot described turbulence event; reported PIREP specifics to FSS; follow up check on PIREP information indicated incorrect FAA data issued; reporter suggesting alternate means of PIREP input.
Narrative: Pilot in Command experienced heavy turbulence and LLWS at XSA; as well as enroute back to flight point of origin at 2W6. Pilot in Command called FSS at the conclusion of the flight to submit a PIREP to advise other GA aircraft in the vicinity of potentially hazardous turbulence. The first PIREP submitted was submitted as a UUA PIREP; describing heavy turbulence and possible LLWS during final approach and landing at XSA. The second PIREP was a UA code; concerning moderate to severe turbulence at about the PXT 240 degree radial at 15 NM at 3;000 FT MSL. The Pilot in Command has a habit of verifying if the PIREP was entered correctly by means of using both ADDS and DUAT. Upon checking both sites; all that was seen (a query for PIREPS submitted over the last 6 hours was used) was a UA PIREP at the PXT 240 degree radial at 5 NM; a P28R reporting light chop. The UUA PIREP submitted for the hazardous conditions at XSA was not entered by the FSS representative. This; in the opinion of the Pilot in Command; represents a potential safety of flight hazard. It is the opinion of the Pilot in Command that there should be a mechanism for reporting PIREPS outside of ATC and FSS. It would be prudent that a website be created or a mechanism within DUAT/DUATS be created to allow pilots to submit PIREPS electronically. This would encourage more pilot weather reporting and contribute to increased flight safety.
Data retrieved from NASA's ASRS site as of April 2012 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.