WESS Aviation Mishap and Hazard Reporting System

(WAMHRS) Aviation Hazard Reporting

Process Lesson Four (8 Nov 2010)

Aviation Mishap/Hazard Entry

Hazard Report have relaxed validation rules. For BASH report you are required to only complete the General information screens, the first aircraft screen and the BASH screen under the aircraft.

For all other hazreps, complete the General Information, Involved Aircraft, Involved Person (only if there are Human Factors, Injury and/or PHYSEP event), Factors, Recommendation, CO's comments and endorsing chain if needed.

For HAZR

For HAZREPs only complete these

Tabs

**Involved Personnel data only required for reports with HFACS, injuries or PHYSEP

Events

Click on each entry screen folder and subfolder to input data. After all data is entered click on Validation

Save at the bottom of each entry screen after inputting data

REPORTING ACTIVITY UIC. Provide UIC of the reporting activity (use squadron or DET UIC, do NOT use ship UIC. If reporting activity is a detachment or composite squadron, provide UIC of parent squadron).

Clicking ‘Yes’ to any of these will bring additional fields for amplifying data

Report latitude and longitude to the nearest minute, except mishaps occurring within 5 NM of an airfield. Latitude/Longitude for these shall be reported to the nearest second

If the mishap occurred aboard a ship or airfield, give the name of the ship or airfield and location on the ship or airfield.

If first two questions are N/A or No, skip rest of Screen

State whether there was distinct or obscured horizon, overcast, undercast, between layers, clear of clouds, in clouds, in-and-out of clouds

Include weather data at time and altitude of mishap: i.e., deck or runway winds, in-flight visibility

Add any individual command if required

Note: This list not active for Hazards

Enter Community

Click to Add Involved Personnel data into data fields

Click to add Factor Folders, click on folder to bring up

data fields to populate, then hit Save

To delete Factor Folders click here, then hit Save

AN E.I. REVEALED LANDING GEAR SYSTEM WAS FULLYOPERATIONAL AT THE TIME OF THE MISHAP AND POST-MISHAPINVESTIGATION AND PHOTOGRAPHS INDICATE THE LANDING GEAR HANDLE IN THE UP POSITION. MISHAP PILOT HAD ONLY FOUR HOURS SLEEP (PC-307) PRIOR TO THE FLIGHT. THE COMMAND DID NOT HAVE AN ADEQUATEDUTY OFFICER INSTRUCTION AND THE DUTY OFFICER CALLED THE PILOT TO ANSWER SCHEDULING QUESTIONS THEREBY, NOT ALLOWING HIM THE REST REQUIRED BY OPNAVINST 3710.7 (SV-001). BASED ON THE ABOVE ANALYSIS THE AMB CONCLUDES THE MISHAP PILOT FAILED TO LOWER THE LANDING GEAR BECAUSE HE LACKED ADEQUATE REST AND WAS DISTRACTED BY A RADIO CALL.

HUMAN FACTOR

PILOT AT CONTROLS FAILED TO LOWER THE LANDINGGEAR

THE PILOT STATED A RADIO CALL INTERRUPTED HISLANDING CHECKS (AE-102, PC-106), BUT HE THOUGHT HE LOWERED THE GEAR.

RAC-1

ACCEPTED.

An example…

Do not check since there is no privileged information in HAZREPs

Recommendations must be tied to a factor

Input comments here. Ensure you hit “Add Comments” Button.

Click to add Endorsing Chain members. Endorsing Chain members are outside Command.

Click to add Routing Chain members. These members are internal to command and up to CO level.

Save Overall Report in the Report Actions drawdown menu

After clicking Validate, you will get a list of validation errors which when clicked on, will take you to the appropriate section to correct

any mistakes or omissions. You will have to click Validate after every correction. Once there are no more validation errors, click Submit

report from Report Actions menu.

Click here to return to

validation errors