Details of request “Industry input into design of Runway 30 RNP-AR flight path

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on Right to Know. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
192052  sent  2023-09-20 07:52:36 +1000  waiting_response  2023-09-20 07:52:36 +1000  waiting_response  outgoing  
202140  response  2023-10-20 12:52:06 +1100    2023-10-20 13:37:23 +1100  waiting_response  incoming  
202143  status_update  2023-10-20 13:37:23 +1100  waiting_response  2023-10-20 13:37:23 +1100  waiting_response   
202331  overdue  2023-10-21 00:00:00 +1100         
211278  very_overdue  2023-11-21 00:00:00 +1100         
211281  followup_sent  2023-11-21 07:54:09 +1100        outgoing  
211292  response  2023-11-21 10:51:53 +1100    2023-11-25 07:39:16 +1100  waiting_response  incoming  
212285  status_update  2023-11-25 07:39:16 +1100  waiting_response  2023-11-25 07:39:16 +1100  waiting_response   
215706  followup_sent  2023-12-13 12:52:43 +1100        outgoing  
215929  followup_sent  2023-12-14 15:32:30 +1100  internal_review  2023-12-14 15:32:31 +1100  internal_review  outgoing  
226700  followup_sent  2024-01-29 17:46:54 +1100        outgoing  
227379  comment  2024-02-01 16:33:19 +1100         
235909  response  2024-02-28 15:40:29 +1100    2024-02-28 15:48:23 +1100  waiting_response  incoming  
235910  followup_sent  2024-02-28 15:48:17 +1100        outgoing  
235911  status_update  2024-02-28 15:48:22 +1100  waiting_response  2024-02-28 15:48:23 +1100  waiting_response   
239902  response  2024-03-13 11:55:11 +1100    2024-03-17 07:42:32 +1100  waiting_response  incoming  
240639  followup_sent  2024-03-17 07:42:19 +1100        outgoing  
240640  status_update  2024-03-17 07:42:32 +1100  waiting_response  2024-03-17 07:42:32 +1100  waiting_response   
296004  edit  2024-09-17 03:45:09 +1000         
296005  edit  2024-09-17 03:45:09 +1000         
296006  edit  2024-09-17 03:45:09 +1000         
296007  edit  2024-09-17 03:45:09 +1000         
296008  edit  2024-09-17 03:45:09 +1000         
296009  edit  2024-09-17 03:45:09 +1000         
296010  edit  2024-09-17 03:45:10 +1000         
296011  edit  2024-09-17 03:45:10 +1000         
296012  edit  2024-09-17 03:45:10 +1000         
296013  edit  2024-09-17 03:45:10 +1000         
296014  edit  2024-09-17 03:45:10 +1000         
296015  edit  2024-09-17 03:45:10 +1000         
296016  edit  2024-09-17 03:45:10 +1000         
296017  edit  2024-09-17 03:45:10 +1000         
296018  edit  2024-09-17 03:45:10 +1000         
296019  edit  2024-09-17 03:45:10 +1000         
296020  edit  2024-09-17 03:45:10 +1000         
296021  edit  2024-09-17 03:45:10 +1000         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by Right to Know for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.