Details of request “Aviation Safety and RPAS (Remotely Piloted Aircraft Systems – ‘drones’) – Whenuapai Control Zone

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
35522 sent 2017-02-21 10:56:05 +1300 waiting_response 2017-02-21 10:56:05 +1300 waiting_response outgoing
35670 followup_sent 2017-02-23 14:42:39 +1300 outgoing
35757 resent 2017-02-24 22:04:21 +1300 waiting_response outgoing
35760 comment 2017-02-24 22:14:14 +1300
37202 response 2017-03-22 12:08:05 +1300 2017-03-22 16:15:26 +1300 waiting_response incoming
37230 followup_sent 2017-03-22 15:52:55 +1300 outgoing
37254 status_update 2017-03-22 16:15:26 +1300 waiting_response 2017-03-22 16:15:26 +1300 waiting_response
37299 response 2017-03-23 11:45:09 +1300 2017-03-23 12:58:59 +1300 waiting_response incoming
37307 followup_sent 2017-03-23 12:58:51 +1300 outgoing
37308 status_update 2017-03-23 12:58:59 +1300 waiting_response 2017-03-23 12:58:59 +1300 waiting_response
37309 followup_sent 2017-03-23 13:01:51 +1300 outgoing
37312 followup_sent 2017-03-23 13:13:20 +1300 outgoing
37313 followup_sent 2017-03-23 13:18:32 +1300 outgoing
37314 followup_sent 2017-03-23 13:25:28 +1300 outgoing
37804 status_update 2017-03-27 20:11:11 +1300 waiting_response 2017-03-27 20:11:11 +1300 waiting_response
38362 response 2017-04-07 10:38:57 +1200 2017-04-09 12:48:11 +1200 waiting_response incoming
38452 followup_sent 2017-04-09 12:48:04 +1200 outgoing
38453 status_update 2017-04-09 12:48:11 +1200 waiting_response 2017-04-09 12:48:11 +1200 waiting_response
38744 response 2017-04-13 11:42:02 +1200 2017-04-25 21:19:30 +1200 waiting_response incoming
39216 followup_sent 2017-04-25 21:19:22 +1200 outgoing
39217 status_update 2017-04-25 21:19:30 +1200 waiting_response 2017-04-25 21:19:30 +1200 waiting_response
39219 followup_sent 2017-04-25 21:41:06 +1200 outgoing
39601 response 2017-05-04 14:52:54 +1200 2017-05-07 21:08:05 +1200 waiting_response incoming
39739 followup_sent 2017-05-07 21:07:49 +1200 outgoing
39740 status_update 2017-05-07 21:08:05 +1200 waiting_response 2017-05-07 21:08:05 +1200 waiting_response
39741 followup_sent 2017-05-07 21:25:18 +1200 outgoing
40060 response 2017-05-16 12:09:07 +1200 2017-06-06 22:54:01 +1200 waiting_response incoming
40950 status_update 2017-06-06 22:54:01 +1200 waiting_response 2017-06-06 22:54:01 +1200 waiting_response
40951 followup_sent 2017-06-06 23:12:09 +1200 outgoing

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 FYI 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.