top of page
Search
Writer's pictureJOY A COLLURA

Archiving Social Media YHFR here on Congress AZ Hillside Fire 7-9-24.


starting from FIRST post to most recent as the last placed here. Then I will remove from FB the YH13' / Dude data only & the current fire situation in my town.


I am in this to document to lead to a conclusion ---


not in it for FB likes and shares...or seek attention...just want as always, a public place to make sure they know some of what I know...


Stop the malarkey here in Congress Arizona.


They reported a smoke check July 9th.


I began documenting from backyard walk on the 10th when winds picked up and I spotted by Mine a huge column of smoke.


Public Records Request Confirmation Number: 00023642


Fire Retardant, Slurry Drop, Phos-chek, any other name used for red chemical with a trade secret dropped on Wildland Fires in Arizona


requesting the 2024 Cooperative Fire Rate Agreements, Intergovernmental Agreement, Agreements of any kind with the red chemical companies tied to your entity, with in addition the amount of funding for 2024 Fire Season used with Arizona State's Department of Forestry and Fire Management in regard to only the red chemical companies, aka fire retardant- fiscal budget. Any records of any agreement changes, amendments in the last 36 months with any current or prior or predicted to become an agreement red chemical company(ies) - aka fire retardant. public records showing how many gallons were used on Hillside Fire in Congress Arizona 7-9-24 until the date this request is filled as well as how many gallons has been used on Wildland Fires in Arizona only in 2024. Any activity logs, unit logs, ICS 214 for Fire Retardant on this incident.



Dates: January until this request is filled.


Topic: Interagency Incident Management Team (IMT) Incident Evaluations for Arizona Wildland Fire Incidents only.


Fire Season 2024


Public Records Request Confirmation Number: 00023643



 


 

 
 
 

 
 

 

 

 
 

 

 
 
 
 


 PRR:

July 9th until DFFM addresses this request- all current-

1. Public Records Request Confirmation Number: 00023594

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890. Resource Order, Resource Orders,

6 aircrafts, 19 engines, Crews 5, Misc Overhead 31









2. Public Records Request Confirmation Number: 00023595

July 9th until DFFM addresses this request- all current-

Incident Action Plans, Incident Actions Plans with I-215 / I-215a

3.Public Records Request Confirmation Number: 00023596

July 9th until DFFM addresses this request- all current-

 all Maps for this fire (both air and ground), any maps tied to this fire.

4Public Records Request Confirmation Number: 00023597

.July 9th until DFFM addresses this request- all current-

any type of Permits and or Special Permits and or Mutual Agreements offered to Ex

ternal Contractors may it be Fire or Media related to this Incident

5.Public Records Request Confirmation Number: 00023598

July 9th until DFFM addresses this request- all current-

Photos, Videos for this Incident in your Entity's possession, within the ones resourced and assigned and actually fighting the fire- any photos that may be on email, emails, or text, texts from Crew Member to your entity or vice versa.
















6Public Records Request Confirmation Number: 00023599

.July 9th until DFFM addresses this request- all current-

Special Interest with Political Inquiries, any politician(s) text or emails in regard to this Incident.

-NO ENGAGEMENT OR INTERACTION

7.Public Records Request Confirmation Number: PRR-423000485

July 9th until DFFM addresses this request- all current-

ICS-201 Incident Briefings

8.Public Records Request Confirmation Number: PRR-423000486

July 9th until DFFM addresses this request- all current-

Field Weather Ops documents may it be in electronic form, email or text

9.July 9th until DFFM addresses this request- all current- Any current financial statements for this Incident

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

 FBAN Report, LTAN Report, IMET Report,

10.July 9th until DFFM addresses this request- all current-

Public Records Request Confirmation Number: PRR-423000487

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

11.Public Records Request Confirmation Number: PRR-423000488

July 9th until DFFM addresses this request- all current-

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

Delegation of Authority Filled out Forms both signed and or unsigned for this Incident,

12. July 9th until DFFM addresses this request- all current-

Public Records Request Confirmation Number: PRR-423000489

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

Assigned Public Information Officer for this Incident. If more than one assigned, all contact information to them. Full Names and Contact Information.

13. Public Records Request Confirmation Number: PRR-423000490

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

Crew Time Reports,

14. PRR-423000491

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344

Emergency Vehicle Shift Tickets

15.Public Records Request Confirmation Number: PRR-423000492

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344 AZPDC-890.

Are you still using ADOT for Fleet Management Data or a new Contractor so I can place that request with proper channels,

I will place one with ADOT yet if it is different please give me the public record that shows the new Fleet Management.

16. Public Records Request Confirmation Number: PRR-423000493

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344

Any AD, Contractors, Safety Officer Crew Time Reports and Emergency Shift Ticket with Inspection Records.

17.Public Records Request Confirmation Number: PRR-423000494

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344

Field Weather Obs, Raws, Lightning Strike records that your entity came to conclusion it was lightning strike because I follow any fire in a ten mile radius and I have yet to see any reported in those area yet I am eyewitness to state they did happen just not in GPS coordinates reported so would like your document so I have something to lead to a conclusion. Thank you.

18. Public Records Request Confirmation Number: PRR-423000495

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344

any aerial recon, slurry drop records, any other type of aerial records

19. Public Records Request Confirmation Number: PRR-423000496

July 9th until DFFM addresses this request- all current

Hillside Fire- Congress, Arizona. 34.213500, -112.849167. 0344

ICS 214 - Unit Logs

That is all I can do for now--- I got to get to sleep-

sleep deprived from this fire. I am in poor health so that has to take priority.

God Bless.

Any record or statement your entity would be willing to make on how come we are placing the safety of firefighters out in the areas of historically significant pockets and cess pools of poisons allowing fire even on this ground and any map showing slurry drop to avoid it being in any creek or waterway areas or even the historically significant pockets and cess pools of poisons- that would be wonderful. Thank you. DFFM

PRR-00023635?

00023635

found this:



July 13, 2024 11:25am:


 

7-14-24 5:35pm- Four Days later- Hillside Congress AZ Wildland Fire 100% out- I was focused there and documenting it.


So, starting tomorrow, I am back to looking at my roots and genealogy.


When I was about to log off- I got this email alert: ????

Rekindled??? Back to documenting...sigh


 

swim time...7:28pm

swim time then crash....long few days...

I would like to get back to my roots but another fire in my area I have to document--- sigh.




Where is your common sense Mr Morris--- the video [snippet down below] was nonsense--- how about stay out of this town / use a dozer and watch how the desert may burn for a bit---but once the wind stops---so does the fire...dumb video: ...operations chief? that is our Leadership???


Help me, Lord. How about keeping your firefighters safe by not placing them out there and placing fire on our ground and the darn red crap...thanks...then I will realize some have common sense when that is done...


is everyone trying to look like BURK MINOR nowadays??? ugh.


In order I received it via email

July 14th:

July 11th:

July 13th:

July 12th:


 

This was about the Moore Ranch reported area fire and the Postal guy saying it was a vehicle incident- DFFM's reply:


 

vehicles unit logs:


This is one of the tools that is good to learn and match the progression to burn scars.


10B550 - 547:

.

  • 09:17:07 - 09:36:17

  • 07/11/2024 11:29:27- Congress Tenderfoot Park then

  • 07/11/2024 19:07:52 to:

  • 07/11/2024 19:12:03 Congress Tenderfoot Park

  • 07/12/2024 09:11:44:

  •  07/12/2024 09:12:16 Seatbelt On until 07/12/2024 09:50:32 34.18837-112.85585 18998 S Cemetery Rd, Congress, AZ 85332, United States

  •   07/12/2024 09:50:47 Seatbelt On S Ghost Town Rd, Congress, AZ 85332, United States

  • 07/12/2024 09:54:06 Congress Tenderfoot Park

  • 07/12/2024 17:53:36

  • 07/12/2024 17:55:06 Congress Tenderfoot Park


 

10B886 - 547

7-11 9:12:15 through 9:20:03 in Glen Ilah area-

the next section- I would want a higher authority of good and are here for us "we, the people" to discuss this area with you - it does matter. To come from Dewey Mayer area to a certain area to Glen Ilah, it does matter...when the fire was in Congress, Arizona not anywhere near that area. I want the higher authority of good to comprehend some areas.



7-11:24 9:43:58 @ Congress Tenderfoot Park until 14:44:47

I am going to break this down because the address led to same spot so using GPS in order:




Appx on one area 2.5hrs-

I would want a higher authority of good and are here for us "we, the people" to discuss this area with you - it does matter.


we were here documenting in person for this fire, so the redaction location does matter especially if EPA is looking at this for their possible investigation since I reported it.


Wherever they went, the odometer shows appx 7 miles, 12 min, 5-12mph.


With the low speed means possible rugged driving??? hmmm...something is off...I know that area for driving and I will be in awe if that person allowed them there ??? Distance, time, mph ??? this is what I called a shelved area ... needs more data.


SEVEN MILES on the odometer...let us see what is near the last shown GPS and radius it out 7 miles:

15:41:00

15:53:24 --- that is 12m 24 seconds--- let us look at Odometer: 27006 - 27013- appx 7 miles reported, and time span was 12m24s and 5-12 speed mph.


The logical place is top of the Date Creek mountains, but we know it is 7 miles but split it in half one way to another and back---


I saw RR's ____ come in and out regularly so that would make sense but haven't seen them to catch up to confirm..."shelved data"


just got a call so I have to start fresh because I do not know where I left off at:


halt---just saw GPS coordinates: let us go relook---I doubt the GPS go to the Cemetery...brb...

thought so: their GPS coordinates does not lead to the Cemetery ??? come on, now.












I am documenting to look at origin / progression / burn scar data - so we can figure out the data and hope the EPA sees the data too if they decided to look into my reporting it.

22716 - 27719 - cemetery, unknown, Tenderfoot Hill Park,


8-23-24 3:29pm: I will pause here --- loads more to place here but you get the point--- EPA can look at Unit Logs and Incident Action Plans and etc...to get a better understanding...I have to do YouTube then genealogy then hopefully back to here--- it is overwhelming the prr data return.

Comentários


bottom of page